[opensuse-kernel] master armv7l configs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPmq33AAoJEB57S2MheeWy2poP/2TF3CWppk2dvZdN9Sahoceu D2Z6I2FTUzyAHpMcl/vEkKRoE9PyOwqRJT+bS1UX2uHqGrO4Sf3RP8RyAmflpTws zAs5ESdCho0u6bwUxEmx5erMAfvFwIH5IFXhmPpuWDymym9xxMxzrK24+toUwCAt u8e6sLETqW5jqD7kStA1xTRu5/jrB6Nu8/AkAZDG9GEm8gr2lEg0cfUMUOPbmk2l 42c1QjwHLlJNhSAXAgHpxFwjht4JuviJEraDpSFJlnk4yozMiI3cTkAeuY/iBRmu 9j5e4M6FHuWCjUOoZ6M2nBBmEz/FMSdtRmgg7vfYTOgkNc1Bire4M2SIcnlXihES jNs/i/AgD37fFGUyGsUrQ7pp35lMi1xTQr4dfzYiYn5vWEHFD1Dv0hP9SNQjrQrm 0JreL5GZdxE3tcnOP95Tt/jMxgITOZe4EqB/rci7HbU5o4Z+oxkFlYRb+v+FSD63 MksZUS5WzCBsIXz2sgUyj1+9TP75ujBgT359KFCzOyXiMZD2416+kS7as9adG4AU axxTavEUDETE5fiKPsBuX8cp5Ctyw3dAKF5hCC/OVjcBGY4qNnt5DTZYR42moh+9 a8vG/DVO4UiOrJh6F7AwBSH7PWwwNNVjsZaToKakThbCqwX3XDcVxCjsLiIQqbgF YhL/Zn7sN9dUvy2ku45b =PrwQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Hi, I forwarded your e-mail to -arm ML. Le 27/04/2012 16:32, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPmriPAAoJEB57S2MheeWyLNMQAJ+8V8JuLuT6Q8+3RWpt8zCC CbTm2sSlcXfAHNmpJ8K0KsdTy568JxcMYokm3LhRyDnauKEfg8Zhe+YPe1nku/2D vY1wOhQ9G9xsm/HpD/KsjUIy3X6RoMS7D74iFcL+vxOaPp3YOGotIi5YpW+70Sw/ k7tqtDWQ9Tzp1aNYB8j+vv3jyFMEX7vJPpFhHoB/EnplWhjWZ/62Y31LE8UygarB aRma9owjPMqL4g2s7vQI/93OCIXhMQnRI4Z1/qfEGBe1W9Fy1pIa4/N/ZCruJHRR UAdeqzCnEnO8rGhtnOlw3lToKWuXnJ7A7vz7y7NBM5BKC8Vl0xO3HrCrlDZUf+7A kdI84wf77M+1PntNEZEYR1tsLA9ISLPGFkINndPQlE/apl+zkSvb3A/2YOGZkKq+ lvSoUWCBo+5tsvR7WvEnVCLpuRlKZwzUS0R6oUJ29+EXvz7tgECbYHzJ9Gvvrqk7 hs35lAZUSpnasITfwn7yItIEPd13JSZDQS3VnV8n2U8tGvcsZPNd4PRmyyhTuCSs mS7FbKgueJa9KgRMz5q7Vu+Nm6bOpSUaEHO2n9D8Jy9gBSUROgPh14sQgUH8AgIO dbXq8V5CJU/9vZ4j/WT+0J77xioT7YhFQ594OjefHm7MX5OoOs77SN5VkB9LG2m3 6YxqZnhCddHbsGoB5sEX =WaIV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Le 27/04/2012 17:17, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/27/2012 11:28 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:17, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPmrtiAAoJEB57S2MheeWyu30P/0dzlbLJTUeqP2WEUd5s7H+Z uFxV2Obb1BkkJgmSh9icLGRO8ZLVmrdUJpE87We2aeCXlXlqOO6BLBS7YCpzsLRw Fp7L6VOmJmVUwh2I+3+yZJz7s61harRspMZzLOALsWp13wIaC8JZbl3skMOhqVGk 6YQqNogshR/P4szLE0SViswggMmLX0q1w42yBdpfsYOll/if/Ifu2T4VFQLMJlJl vClhoctiQ7GmETk4waL/L4pc7xOJv5fXeiuANEv3DuvupBTqlw2sJ2cGc04Bcj98 FmliMFGqJ39/pWxaLGcDJRmd3QqFsweMvL7AUaQH1TIhmDDjXv3ASi4KMwXNbn5R 7ix0B247ekToua8i8fE4EHotN+GC12X9NlF+MB2/Fx55IXhoxW1cUqdq5I8twkED GVjJA4K/5ff7BaB6pZsYF7vIHLwWgtW3X1Svd8dgnuPxUA+hSE+E7JEHqqgk1xlJ hWFrK8VcPQGfiam+XtvEdwSVWvc2Q5AAo6XdEyAQlYdoOcX5uC1xUMTu8sCC+Ayf A+PdmpSF8qR2nOe9eYCq4Dx+BKFxObMbEanMLjO7wJvBK+WcK1jTCe1P1lWORc1N Igj0JTMVxt4i+CYGNCQIRnRdU84L/YoPCc1mcyyNfdUQ0LeB1jPEPCkSqIEzQuZR jibBA1+maP03XYzMzeMd =alVy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Le 27/04/2012 17:29, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/27/2012 11:28 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:17, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/27/2012 11:36 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:29, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/27/2012 11:28 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:17, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPmr2XAAoJEB57S2MheeWyT+sP+QFlOM7pajwjjlvOCDET4+Ve VGQHeRR7N4cDHtwYVz2473RhhplaGD1YJRtiPKdO9JA95Ny5cCROWzP+lrKtenLY 4fGq4auerYSsZiqv9XNsxj4ndD40c+aNAKMS67T0EA2Yp3sIcGC8pnywDi/vbbBt eYruViFVDlMhRUr+DBFvxSeuBi5HTVgDbWBUzOs/6Cd+0K/lYa69Co5G+1wnbRLS Ie8WDEGEKZk0p3OkgoPg4pWgdz81WKPjWTMJXBpCz+4FyVX9bYs1Or/4DjFxQyNn cwCrW57Pms1HOTIrYR9DlMKdKKYXQEzmOxJC06Q9zsoIRqFEgv4bOTxp1eVYaNIj y2nZhMPQDVWvDvGsB/5pCP/+KpiUyo3lKc8VoEbkbKMew73BKkwDIbvJwa3Lqhlt sW2QTWDK7Dh2JNL9LvIHhU1bXXbEoQZE4465VEOAE85Sa2fAfa/vrW0huYXU7dL/ 5+uTbFSrkKexf12VueJDmBYA20/aFypym11StLig4r8hEVfXPkLXJQvK31OeM9/F cQFd7ozOhyrv3Sf5PO9fOutPkNP7ZgT7iD4g+hR4akIooU2g0hrsi/aId6O/wbO6 IJ0WCfXiDz2E5CgrzdgFCP0jXr/BU6wYp7qmkB+JUKXLNntuRVJZFMWRxAvP1h+m c2gNc8C8m8O2THmI9UQG =FqPp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Le 27/04/2012 17:39, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/27/2012 11:36 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:29, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/27/2012 11:28 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:17, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 : > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > 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 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
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 <guillaume.gardet@opensuse.org> * openSUSE-update-config-armv7l-default.patch update ARM default config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org> *openSUSE-update-config-armv7l-imx51.patch update ARM imx51 config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org> * openSUSE-update-config-armv7l-omap2plus.patch update ARM omap2plus config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org> * openSUSE-update-config-armv7l-tegra.patch update ARM tegra config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org> * openSUSE-update-config-armv7l-u8500.patch update ARM u8500 config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org> signed-off-by: Andrew Wafaa <awafaa@opensuse.org> Regards, Guillaume Le 30/04/2012 13:05, Guillaume Gardet a écrit :
Le 27/04/2012 17:39, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/27/2012 11:36 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:29, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/27/2012 11:28 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:17, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 : >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 <guillaume.gardet@opensuse.org>
* openSUSE-update-config-armv7l-default.patch update ARM default config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org>
*openSUSE-update-config-armv7l-imx51.patch update ARM imx51 config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org>
* openSUSE-update-config-armv7l-omap2plus.patch update ARM omap2plus config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org>
* openSUSE-update-config-armv7l-tegra.patch update ARM tegra config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org>
* openSUSE-update-config-armv7l-u8500.patch update ARM u8500 config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org> signed-off-by: Andrew Wafaa <awafaa@opensuse.org>
Regards,
Guillaume
Le 30/04/2012 13:05, Guillaume Gardet a écrit :
Le 27/04/2012 17:39, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/27/2012 11:36 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:29, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/27/2012 11:28 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:17, Jeff Mahoney a écrit : > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > 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 : >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>> >>> 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPnvmPAAoJEB57S2MheeWy/B4P/RkltHGsPjWZ9+gzovD8B45t aBc70FJYne8qvssRdAznazS7ULR/EKW8gfKTksXcEunKa0KBMvKWmPUVCHCKCusX NiHyw/gFi0pqkzj8YeLq0RJXXQLufF506EZ8IlLe9sOMQXktNrg2lwqJcATPxIh4 Ca4DFeI8iNc3sc5C96HFxy6TO4QmmCRU3njBi452GDqfRDCQa7Pg+3k4Gt9De5Z9 YJ0dv/1W/05IJnQDqd9f5v5obCUU8mLrX9ilhDqFHQnWkrCuVx7YW5dJyOiDGlfx q1321X13+/sL8KHh35IwCTC47mEyIaC1aQpHplx3IPNdQ4hdlRpl4ETEdzJYnrwI 8UK+Pmw5fKXdP01WH0Gw1xs4xrM05klTXVk6M8weOgzmsjhf6nbuWjSBabY3+wqP AZjUudznEGXJAlBMJvbUaehOiO92YUUTFkHggksthO6yPWAOzNDk5Barrt5BXKJs 2tCULKrJ7xaJp8rZe+lBjzUzs7b19zr9bBW9H6WM4rE+9XBY/ybuyV02t65Hphvd aLBOvGMm5a5rjpo0nXdJEekv6qMi8LbjANHm8UTexVYI1C2SZR6DXDsj5Klf7C4g SacF2HP7QCi25fgTNxyo4L9/0UD7VlqhIL6tlyuQ+Fk5mIvYlSopikjpaJBYLdf/ 7CKUhtgFWSIUnUIL20PY =Lhqp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Le 30/04/2012 22:43, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 <guillaume.gardet@opensuse.org>
* openSUSE-update-config-armv7l-default.patch update ARM default config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org>
*openSUSE-update-config-armv7l-imx51.patch update ARM imx51 config signed-off-by: Guillaume GARDET<guillaume.gardet@opensuse.org>
* openSUSE-update-config-armv7l-omap2plus.patch update ARM omap2plus config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org>
* openSUSE-update-config-armv7l-tegra.patch update ARM tegra config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org>
* openSUSE-update-config-armv7l-u8500.patch update ARM u8500 config signed-off-by: Guillaume GARDET <guillaume.gardet@opensuse.org> signed-off-by: Andrew Wafaa <awafaa@opensuse.org>
Regards,
Guillaume
Le 30/04/2012 13:05, Guillaume Gardet a écrit :
Le 27/04/2012 17:39, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/27/2012 11:36 AM, Guillaume Gardet wrote:
Le 27/04/2012 17:29, Jeff Mahoney a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/27/2012 11:28 AM, Guillaume Gardet wrote: > Le 27/04/2012 17:17, Jeff Mahoney a écrit : >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> 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 : >>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>> >>>> 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPnvmPAAoJEB57S2MheeWy/B4P/RkltHGsPjWZ9+gzovD8B45t aBc70FJYne8qvssRdAznazS7ULR/EKW8gfKTksXcEunKa0KBMvKWmPUVCHCKCusX NiHyw/gFi0pqkzj8YeLq0RJXXQLufF506EZ8IlLe9sOMQXktNrg2lwqJcATPxIh4 Ca4DFeI8iNc3sc5C96HFxy6TO4QmmCRU3njBi452GDqfRDCQa7Pg+3k4Gt9De5Z9 YJ0dv/1W/05IJnQDqd9f5v5obCUU8mLrX9ilhDqFHQnWkrCuVx7YW5dJyOiDGlfx q1321X13+/sL8KHh35IwCTC47mEyIaC1aQpHplx3IPNdQ4hdlRpl4ETEdzJYnrwI 8UK+Pmw5fKXdP01WH0Gw1xs4xrM05klTXVk6M8weOgzmsjhf6nbuWjSBabY3+wqP AZjUudznEGXJAlBMJvbUaehOiO92YUUTFkHggksthO6yPWAOzNDk5Barrt5BXKJs 2tCULKrJ7xaJp8rZe+lBjzUzs7b19zr9bBW9H6WM4rE+9XBY/ybuyV02t65Hphvd aLBOvGMm5a5rjpo0nXdJEekv6qMi8LbjANHm8UTexVYI1C2SZR6DXDsj5Klf7C4g SacF2HP7QCi25fgTNxyo4L9/0UD7VlqhIL6tlyuQ+Fk5mIvYlSopikjpaJBYLdf/ 7CKUhtgFWSIUnUIL20PY =Lhqp -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (2)
-
Guillaume Gardet -
Jeff Mahoney