Hi all -
When I merged 3.4-rc1, I disabled ARM builds. I'd like to re-enable
them now, but have no idea what the ARM guys want for config options.
Can someone go through and sync the configs up and send a patch/pull
request for the new configs that also enable armv7l in config.conf?
Thanks.
- -Jeff
Hi, I forwarded your e-mail to -arm ML.Le 27/04/2012 16:32, Jeff Mahoney a écrit :> > Hi all - > > When I merged 3.4-rc1, I disabled ARM builds. I'd like to re-enable > them now, but have no idea what the ARM guys want for config options.What do you mean exactly? Must we just update the ARM config files manually or do you have some auto script to use?> > Can someone go through and sync the configs up and send a patch/pull > request for the new configs that also enable armv7l in config.conf?For config.conf, we just need to remove the '#'? Guillaume
On 04/27/2012 11:03 AM, Guillaume Gardet wrote: > Hi, > > I forwarded your e-mail to -arm ML. > > Le 27/04/2012 16:32, Jeff Mahoney a écrit :>> >> Hi all - >> >> When I merged 3.4-rc1, I disabled ARM builds. I'd like to >> re-enable them now, but have no idea what the ARM guys want for >> config options. > > What do you mean exactly? Must we just update the ARM config files > manually or do you have some auto script to use?You can git diff between the -rc1 update and current to see what's changed, but since those arm boards tend to be pretty specific, there may be some hand-tuning involved. The most convenient way is to add the new options you know you want to each config manually (or by script), enable armv7l in config.conf, expand the source tree, and while cd'd into the source tree, do patches/scripts/run_oldconfig.sh -a armv7l>> >> Can someone go through and sync the configs up and send a >> patch/pull request for the new configs that also enable armv7l in >> config.conf? > > For config.conf, we just need to remove the '#'?Yep. - -Jeff
Le 27/04/2012 17:17, Jeff Mahoney a écrit :> > On 04/27/2012 11:03 AM, Guillaume Gardet wrote: >> Hi, >> >> I forwarded your e-mail to -arm ML. >> >> Le 27/04/2012 16:32, Jeff Mahoney a écrit :>>> >>> Hi all - >>> >>> When I merged 3.4-rc1, I disabled ARM builds. I'd like to >>> re-enable them now, but have no idea what the ARM guys want for >>> config options. >> What do you mean exactly? Must we just update the ARM config files >> manually or do you have some auto script to use? > You can git diff between the -rc1 update and current to see what's > changed, but since those arm boards tend to be pretty specific, there > may be some hand-tuning involved.Yes. There are also lots of "old" options wanted but not yet enabled.> > The most convenient way is to add the new options you know you want to > each config manually (or by script), enable armv7l in config.conf, > expand the source tree, and while cd'd into the source tree, do > patches/scripts/run_oldconfig.sh -a armv7l > >>> Can someone go through and sync the configs up and send a >>> patch/pull request for the new configs that also enable armv7l in >>> config.conf? >> For config.conf, we just need to remove the '#'? > Yep.Ok. We will discuss it on -arm ML and we will send you patches. Is there a deadline? Guillaume
On 04/27/2012 11:28 AM, Guillaume Gardet wrote: > > > Le 27/04/2012 17:17, Jeff Mahoney a écrit :>> >> On 04/27/2012 11:03 AM, Guillaume Gardet wrote: >>> Hi, >>> >>> I forwarded your e-mail to -arm ML. >>> >>> Le 27/04/2012 16:32, Jeff Mahoney a écrit :>>>> >>>> Hi all - >>>> >>>> When I merged 3.4-rc1, I disabled ARM builds. I'd like to >>>> re-enable them now, but have no idea what the ARM guys want >>>> for config options. >>> What do you mean exactly? Must we just update the ARM config >>> files manually or do you have some auto script to use? >> You can git diff between the -rc1 update and current to see >> what's changed, but since those arm boards tend to be pretty >> specific, there may be some hand-tuning involved. > > Yes. There are also lots of "old" options wanted but not yet > enabled. > >> >> The most convenient way is to add the new options you know you >> want to each config manually (or by script), enable armv7l in >> config.conf, expand the source tree, and while cd'd into the >> source tree, do patches/scripts/run_oldconfig.sh -a armv7l >> >>>> Can someone go through and sync the configs up and send a >>>> patch/pull request for the new configs that also enable >>>> armv7l in config.conf? >>> For config.conf, we just need to remove the '#'? >> Yep. > > Ok. > > We will discuss it on -arm ML and we will send you patches. Is > there a deadline?Not strictly, but I can't submit the new kernel to Factory until it's complete. - -Jeff
Le 27/04/2012 17:29, Jeff Mahoney a écrit :>
> On 04/27/2012 11:28 AM, Guillaume Gardet wrote:
>>
>> Le 27/04/2012 17:17, Jeff Mahoney a écrit :>>>
>>> On 04/27/2012 11:03 AM, Guillaume Gardet wrote:
>>>> Hi,
>>>>
>>>> I forwarded your e-mail to -arm ML.
>>>>
>>>> Le 27/04/2012 16:32, Jeff Mahoney a écrit :>>>>>
>>>>> Hi all -
>>>>>
>>>>> When I merged 3.4-rc1, I disabled ARM builds. I'd like to
>>>>> re-enable them now, but have no idea what the ARM guys want
>>>>> for config options.
>>>> What do you mean exactly? Must we just update the ARM config
>>>> files manually or do you have some auto script to use?
>>> You can git diff between the -rc1 update and current to see
>>> what's changed, but since those arm boards tend to be pretty
>>> specific, there may be some hand-tuning involved.
>> Yes. There are also lots of "old" options wanted but not yet
>> enabled.
>>
>>> The most convenient way is to add the new options you know you
>>> want to each config manually (or by script), enable armv7l in
>>> config.conf, expand the source tree, and while cd'd into the
>>> source tree, do patches/scripts/run_oldconfig.sh -a armv7l
>>>
>>>>> Can someone go through and sync the configs up and send a
>>>>> patch/pull request for the new configs that also enable
>>>>> armv7l in config.conf?
>>>> For config.conf, we just need to remove the '#'?
>>> Yep.
>> Ok.
>>
>> We will discuss it on -arm ML and we will send you patches. Is
>> there a deadline?
> Not strictly, but I can't submit the new kernel to Factory until it's
> complete.Ok. So, the best thing we can do is a quick review now and send more patches later if needed.
Would you be OK with this way?
Guillaume
On 04/27/2012 11:36 AM, Guillaume Gardet wrote: > > > Le 27/04/2012 17:29, Jeff Mahoney a écrit :>> >> On 04/27/2012 11:28 AM, Guillaume Gardet wrote: >>> >>> Le 27/04/2012 17:17, Jeff Mahoney a écrit :>>>> >>>> On 04/27/2012 11:03 AM, Guillaume Gardet wrote: >>>>> Hi, >>>>> >>>>> I forwarded your e-mail to -arm ML. >>>>> >>>>> Le 27/04/2012 16:32, Jeff Mahoney a écrit :>>>>>> >>>>>> Hi all - >>>>>> >>>>>> When I merged 3.4-rc1, I disabled ARM builds. I'd like >>>>>> to re-enable them now, but have no idea what the ARM guys >>>>>> want for config options. >>>>> What do you mean exactly? Must we just update the ARM >>>>> config files manually or do you have some auto script to >>>>> use? >>>> You can git diff between the -rc1 update and current to see >>>> what's changed, but since those arm boards tend to be pretty >>>> specific, there may be some hand-tuning involved. >>> Yes. There are also lots of "old" options wanted but not yet >>> enabled. >>> >>>> The most convenient way is to add the new options you know >>>> you want to each config manually (or by script), enable >>>> armv7l in config.conf, expand the source tree, and while cd'd >>>> into the source tree, do patches/scripts/run_oldconfig.sh -a >>>> armv7l >>>> >>>>>> Can someone go through and sync the configs up and send >>>>>> a patch/pull request for the new configs that also >>>>>> enable armv7l in config.conf? >>>>> For config.conf, we just need to remove the '#'? >>>> Yep. >>> Ok. >>> >>> We will discuss it on -arm ML and we will send you patches. Is >>> there a deadline? >> Not strictly, but I can't submit the new kernel to Factory until >> it's complete. > > Ok. So, the best thing we can do is a quick review now and send > more patches later if needed. > > Would you be OK with this way?Yep, that's fine with me. - -Jeff
Le 27/04/2012 17:39, Jeff Mahoney a écrit :>
> On 04/27/2012 11:36 AM, Guillaume Gardet wrote:
>>
>> Le 27/04/2012 17:29, Jeff Mahoney a écrit :>>>
>>> On 04/27/2012 11:28 AM, Guillaume Gardet wrote:
>>>> Le 27/04/2012 17:17, Jeff Mahoney a écrit :>>>>>
>>>>> On 04/27/2012 11:03 AM, Guillaume Gardet wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I forwarded your e-mail to -arm ML.
>>>>>>
>>>>>> Le 27/04/2012 16:32, Jeff Mahoney a écrit :>>>>>>>
>>>>>>> Hi all -
>>>>>>>
>>>>>>> When I merged 3.4-rc1, I disabled ARM builds. I'd like
>>>>>>> to re-enable them now, but have no idea what the ARM guys
>>>>>>> want for config options.
>>>>>> What do you mean exactly? Must we just update the ARM
>>>>>> config files manually or do you have some auto script to
>>>>>> use?
>>>>> You can git diff between the -rc1 update and current to see
>>>>> what's changed, but since those arm boards tend to be pretty
>>>>> specific, there may be some hand-tuning involved.
>>>> Yes. There are also lots of "old" options wanted but not yet
>>>> enabled.
>>>>
>>>>> The most convenient way is to add the new options you know
>>>>> you want to each config manually (or by script), enable
>>>>> armv7l in config.conf, expand the source tree, and while cd'd
>>>>> into the source tree, do patches/scripts/run_oldconfig.sh -a
>>>>> armv7l
>>>>>
>>>>>>> Can someone go through and sync the configs up and send
>>>>>>> a patch/pull request for the new configs that also
>>>>>>> enable armv7l in config.conf?
>>>>>> For config.conf, we just need to remove the '#'?
>>>>> Yep.
>>>> Ok.
>>>>
>>>> We will discuss it on -arm ML and we will send you patches. Is
>>>> there a deadline?
>>> Not strictly, but I can't submit the new kernel to Factory until
>>> it's complete.
>> Ok. So, the best thing we can do is a quick review now and send
>> more patches later if needed.
>>
>> Would you be OK with this way?
> Yep, that's fine with me.I will send patches for ARM configs today (or maybe tomorrow).
Guillaume
Hi,
Please find in attachment the patch series for ARM config:
* enable-ARM-build-in-config.conf.patch :
re-enable ARM arch in config.conf
signed-off-by: Guillaume GARDET
* openSUSE-update-config-armv7l-default.patch
update ARM default config
signed-off-by: Guillaume GARDET
*openSUSE-update-config-armv7l-imx51.patch
update ARM imx51 config
signed-off-by: Guillaume GARDET
* openSUSE-update-config-armv7l-omap2plus.patch
update ARM omap2plus config
signed-off-by: Guillaume GARDET
* openSUSE-update-config-armv7l-tegra.patch
update ARM tegra config
signed-off-by: Guillaume GARDET
* openSUSE-update-config-armv7l-u8500.patch
update ARM u8500 config
signed-off-by: Guillaume GARDET
signed-off-by: Andrew Wafaa
Regards,
GuillaumeLe 30/04/2012 13:05, Guillaume Gardet a écrit :
>
>
> Le 27/04/2012 17:39, Jeff Mahoney a écrit :>>
>> On 04/27/2012 11:36 AM, Guillaume Gardet wrote:
>>>
>>> Le 27/04/2012 17:29, Jeff Mahoney a écrit :>>>>
>>>> On 04/27/2012 11:28 AM, Guillaume Gardet wrote:
>>>>> Le 27/04/2012 17:17, Jeff Mahoney a écrit :>>>>>>
>>>>>> On 04/27/2012 11:03 AM, Guillaume Gardet wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I forwarded your e-mail to -arm ML.
>>>>>>>
>>>>>>> Le 27/04/2012 16:32, Jeff Mahoney a écrit :>>>>>>>>
>>>>>>>> Hi all -
>>>>>>>>
>>>>>>>> When I merged 3.4-rc1, I disabled ARM builds. I'd like
>>>>>>>> to re-enable them now, but have no idea what the ARM guys
>>>>>>>> want for config options.
>>>>>>> What do you mean exactly? Must we just update the ARM
>>>>>>> config files manually or do you have some auto script to
>>>>>>> use?
>>>>>> You can git diff between the -rc1 update and current to see
>>>>>> what's changed, but since those arm boards tend to be pretty
>>>>>> specific, there may be some hand-tuning involved.
>>>>> Yes. There are also lots of "old" options wanted but not yet
>>>>> enabled.
>>>>>
>>>>>> The most convenient way is to add the new options you know
>>>>>> you want to each config manually (or by script), enable
>>>>>> armv7l in config.conf, expand the source tree, and while cd'd
>>>>>> into the source tree, do patches/scripts/run_oldconfig.sh -a
>>>>>> armv7l
>>>>>>
>>>>>>>> Can someone go through and sync the configs up and send
>>>>>>>> a patch/pull request for the new configs that also
>>>>>>>> enable armv7l in config.conf?
>>>>>>> For config.conf, we just need to remove the '#'?
>>>>>> Yep.
>>>>> Ok.
>>>>>
>>>>> We will discuss it on -arm ML and we will send you patches. Is
>>>>> there a deadline?
>>>> Not strictly, but I can't submit the new kernel to Factory until
>>>> it's complete.
>>> Ok. So, the best thing we can do is a quick review now and send
>>> more patches later if needed.
>>>
>>> Would you be OK with this way?
>> Yep, that's fine with me.
>
> I will send patches for ARM configs today (or maybe tomorrow).
>
>
> Guillaume
>
On 04/30/2012 04:36 PM, Guillaume Gardet wrote: > Hi, > > Please find in attachment the patch series for ARM config:Thanks. Merged and pushed. BTW, I just merged all of the patches as one and made a simple commit. For individual patches to be properly logged and credited, they need full patch headers so that I can import them with git-am. Alternatively, a git pull request would work. In this case, a single patch doing everything would've been fine since the configs are all separate anyway. - -Jeff> * enable-ARM-build-in-config.conf.patch : re-enable ARM arch in > config.conf signed-off-by: Guillaume GARDET > > > * openSUSE-update-config-armv7l-default.patch update ARM default > config signed-off-by: Guillaume GARDET > > > *openSUSE-update-config-armv7l-imx51.patch update ARM imx51 config > signed-off-by: Guillaume GARDET > > * openSUSE-update-config-armv7l-omap2plus.patch update ARM > omap2plus config signed-off-by: Guillaume GARDET > > > * openSUSE-update-config-armv7l-tegra.patch update ARM tegra > config signed-off-by: Guillaume GARDET > > > * openSUSE-update-config-armv7l-u8500.patch update ARM u8500 > config signed-off-by: Guillaume GARDET > signed-off-by: Andrew Wafaa > > > > Regards, > > Guillaume > > > > > > Le 30/04/2012 13:05, Guillaume Gardet a écrit : >> >> >> Le 27/04/2012 17:39, Jeff Mahoney a écrit :>>> >>> On 04/27/2012 11:36 AM, Guillaume Gardet wrote: >>>> >>>> Le 27/04/2012 17:29, Jeff Mahoney a écrit :>>>>> >>>>> On 04/27/2012 11:28 AM, Guillaume Gardet wrote: >>>>>> Le 27/04/2012 17:17, Jeff Mahoney a écrit :>>>>>>> >>>>>>> On 04/27/2012 11:03 AM, Guillaume Gardet wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> I forwarded your e-mail to -arm ML. >>>>>>>> >>>>>>>> Le 27/04/2012 16:32, Jeff Mahoney a écrit :>>>>>>>>> >>>>>>>>> Hi all - >>>>>>>>> >>>>>>>>> When I merged 3.4-rc1, I disabled ARM builds. I'd >>>>>>>>> like to re-enable them now, but have no idea what >>>>>>>>> the ARM guys want for config options. >>>>>>>> What do you mean exactly? Must we just update the >>>>>>>> ARM config files manually or do you have some auto >>>>>>>> script to use? >>>>>>> You can git diff between the -rc1 update and current to >>>>>>> see what's changed, but since those arm boards tend to >>>>>>> be pretty specific, there may be some hand-tuning >>>>>>> involved. >>>>>> Yes. There are also lots of "old" options wanted but not >>>>>> yet enabled. >>>>>> >>>>>>> The most convenient way is to add the new options you >>>>>>> know you want to each config manually (or by script), >>>>>>> enable armv7l in config.conf, expand the source tree, >>>>>>> and while cd'd into the source tree, do >>>>>>> patches/scripts/run_oldconfig.sh -a armv7l >>>>>>> >>>>>>>>> Can someone go through and sync the configs up and >>>>>>>>> send a patch/pull request for the new configs that >>>>>>>>> also enable armv7l in config.conf? >>>>>>>> For config.conf, we just need to remove the '#'? >>>>>>> Yep. >>>>>> Ok. >>>>>> >>>>>> We will discuss it on -arm ML and we will send you >>>>>> patches. Is there a deadline? >>>>> Not strictly, but I can't submit the new kernel to Factory >>>>> until it's complete. >>>> Ok. So, the best thing we can do is a quick review now and >>>> send more patches later if needed. >>>> >>>> Would you be OK with this way? >>> Yep, that's fine with me. >> >> I will send patches for ARM configs today (or maybe tomorrow). >> >> >> Guillaume >>
Le 30/04/2012 22:43, Jeff Mahoney a écrit :> > On 04/30/2012 04:36 PM, Guillaume Gardet wrote: >> Hi, >> >> Please find in attachment the patch series for ARM config: > Thanks. Merged and pushed. > > BTW, I just merged all of the patches as one and made a simple commit. > For individual patches to be properly logged and credited, they need > full patch headers so that I can import them with git-am. > Alternatively, a git pull request would work. > > In this case, a single patch doing everything would've been fine since > the configs are all separate anyway.Ok. Next time I will do it in a proper way. Thanks. Guillaume> > - -Jeff > > >> * enable-ARM-build-in-config.conf.patch : re-enable ARM arch in >> config.conf signed-off-by: Guillaume GARDET >> >> >> * openSUSE-update-config-armv7l-default.patch update ARM default >> config signed-off-by: Guillaume GARDET >> >> >> *openSUSE-update-config-armv7l-imx51.patch update ARM imx51 config >> signed-off-by: Guillaume GARDET< >> >> * openSUSE-update-config-armv7l-omap2plus.patch update ARM >> omap2plus config signed-off-by: Guillaume GARDET >> >> >> * openSUSE-update-config-armv7l-tegra.patch update ARM tegra >> config signed-off-by: Guillaume GARDET >> >> >> * openSUSE-update-config-armv7l-u8500.patch update ARM u8500 >> config signed-off-by: Guillaume GARDET >> signed-off-by: Andrew Wafaa >> >> >> >> Regards, >> >> Guillaume >> >> >> >> >> >> Le 30/04/2012 13:05, Guillaume Gardet a écrit : >>> >>> Le 27/04/2012 17:39, Jeff Mahoney a écrit :>>>> >>>> On 04/27/2012 11:36 AM, Guillaume Gardet wrote: >>>>> Le 27/04/2012 17:29, Jeff Mahoney a écrit :>>>>>> >>>>>> On 04/27/2012 11:28 AM, Guillaume Gardet wrote: >>>>>>> Le 27/04/2012 17:17, Jeff Mahoney a écrit :>>>>>>>> >>>>>>>> On 04/27/2012 11:03 AM, Guillaume Gardet wrote: >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I forwarded your e-mail to -arm ML. >>>>>>>>> >>>>>>>>> Le 27/04/2012 16:32, Jeff Mahoney a écrit :>>>>>>>>>> >>>>>>>>>> Hi all - >>>>>>>>>> >>>>>>>>>> When I merged 3.4-rc1, I disabled ARM builds. I'd >>>>>>>>>> like to re-enable them now, but have no idea what >>>>>>>>>> the ARM guys want for config options. >>>>>>>>> What do you mean exactly? Must we just update the >>>>>>>>> ARM config files manually or do you have some auto >>>>>>>>> script to use? >>>>>>>> You can git diff between the -rc1 update and current to >>>>>>>> see what's changed, but since those arm boards tend to >>>>>>>> be pretty specific, there may be some hand-tuning >>>>>>>> involved. >>>>>>> Yes. There are also lots of "old" options wanted but not >>>>>>> yet enabled. >>>>>>> >>>>>>>> The most convenient way is to add the new options you >>>>>>>> know you want to each config manually (or by script), >>>>>>>> enable armv7l in config.conf, expand the source tree, >>>>>>>> and while cd'd into the source tree, do >>>>>>>> patches/scripts/run_oldconfig.sh -a armv7l >>>>>>>> >>>>>>>>>> Can someone go through and sync the configs up and >>>>>>>>>> send a patch/pull request for the new configs that >>>>>>>>>> also enable armv7l in config.conf? >>>>>>>>> For config.conf, we just need to remove the '#'? >>>>>>>> Yep. >>>>>>> Ok. >>>>>>> >>>>>>> We will discuss it on -arm ML and we will send you >>>>>>> patches. Is there a deadline? >>>>>> Not strictly, but I can't submit the new kernel to Factory >>>>>> until it's complete. >>>>> Ok. So, the best thing we can do is a quick review now and >>>>> send more patches later if needed. >>>>> >>>>> Would you be OK with this way? >>>> Yep, that's fine with me. >>> I will send patches for ARM configs today (or maybe tomorrow). >>> >>> >>> Guillaume >>> > > - -- > Jeff Mahoney > SUSE Labs >