Message ID | 20120108034408.GB19721@S2101-09.ap.freescale.net |
---|---|
State | New |
Headers | show |
On Sun, Jan 08, 2012 at 11:44:10AM +0800, Shawn Guo wrote: > Hi Arnd, Olof, > > As I promised to Lauri, I will send his board support for 3.3. I know > even if it gets pulled, it will go to 'late/*' which is not guaranteed > to be sent for 3.3. But anyway, here it is. Please consider to pull. > I forgot to mention that it has a dependency on arm-soc/mxs/saif. But since it will go to late/* and the mxs/saif already hits next/*, the dependency can be sorted out easily, I guess.
On 01/09/2012 04:20 AM, Shawn Guo wrote: > On Sun, Jan 08, 2012 at 11:44:10AM +0800, Shawn Guo wrote: >> Hi Arnd, Olof, >> >> As I promised to Lauri, I will send his board support for 3.3. I know >> even if it gets pulled, it will go to 'late/*' which is not guaranteed >> to be sent for 3.3. But anyway, here it is. Please consider to pull. >> > I forgot to mention that it has a dependency on arm-soc/mxs/saif. But > since it will go to late/* and the mxs/saif already hits next/*, the > dependency can be sorted out easily, I guess. Just to ask what's the status of this pull request? I would't like to wait next merge window again. Patch was missed already previous (3.2) one. Regards, Lauri Hintsala
On 01/20/2012 09:20 AM, Shawn Guo wrote: > Sadly, it seems that we have to wait for the next merge window, since > I do not see it in the v3.3-rc1. Ok, I'll add restart hooks to machine code, fix the saif issue and send new version soon. Let's try to get it to 3.4 :) BR, Lauri
On Fri, Jan 20, 2012 at 09:00:47AM +0200, Lauri Hintsala wrote: > On 01/09/2012 04:20 AM, Shawn Guo wrote: > >On Sun, Jan 08, 2012 at 11:44:10AM +0800, Shawn Guo wrote: > >>Hi Arnd, Olof, > >> > >>As I promised to Lauri, I will send his board support for 3.3. I know > >>even if it gets pulled, it will go to 'late/*' which is not guaranteed > >>to be sent for 3.3. But anyway, here it is. Please consider to pull. > >> > >I forgot to mention that it has a dependency on arm-soc/mxs/saif. But > >since it will go to late/* and the mxs/saif already hits next/*, the > >dependency can be sorted out easily, I guess. > > Just to ask what's the status of this pull request? I would't like > to wait next merge window again. Patch was missed already previous > (3.2) one. > Sadly, it seems that we have to wait for the next merge window, since I do not see it in the v3.3-rc1.
On Fri, Jan 20, 2012 at 09:13:53AM +0200, Lauri Hintsala wrote: > On 01/20/2012 09:20 AM, Shawn Guo wrote: > >Sadly, it seems that we have to wait for the next merge window, since > >I do not see it in the v3.3-rc1. > > Ok, I'll add restart hooks to machine code, fix the saif issue and > send new version soon. Let's try to get it to 3.4 :) > Arnd, Olof, Please ignore this pull request then. We will come up with a new one for 3.4 later.
On Friday 20 January 2012, Shawn Guo wrote: > On Fri, Jan 20, 2012 at 09:13:53AM +0200, Lauri Hintsala wrote: > > On 01/20/2012 09:20 AM, Shawn Guo wrote: > > >Sadly, it seems that we have to wait for the next merge window, since > > >I do not see it in the v3.3-rc1. > > > > Ok, I'll add restart hooks to machine code, fix the saif issue and > > send new version soon. Let's try to get it to 3.4 :) > > > Arnd, Olof, > > Please ignore this pull request then. We will come up with a new one > for 3.4 later. Ok, sounds good. I'm sorry that these patches got delayed so long, but I wasn't aware of them until the pull request on Jan 8, and by that time it was certainly too late. Please just send a new pull request based on 3.3-rc1 in the next days and it should be no problem at all to get them in to 3.4. Arnd