Skip to contentSkip to conversation

Upcoming merge window, marked all the patchwork patches before v2.6.35 as archived

DISCUSSION Tony Lindgren 2 participants 3 messages Sep 15, 2010

lore
Share & tools
lore
#0 lore raw

Hi all,

Here's some important info regarding posted patches and the upcoming merge window.

UPCOMING MERGE WINDOW

Just to remind everybody, we want to have our omap patches reviewed and queued into for-next by -rc6. That is less than two weeks from today.

If you have a larger set of patches, please set them up into a git branch after review for pulling. Please remember that anything touching arch/arm/*omap*/ must be also reviewed on the linux-arm-kernel list, so Cc that list too so I don't have to repost the patches before applying. Basically see the instructions here (server currently down?):

http://www.elinux.org/OMAP_patch_merging_process

POSTED PATCHES AND PATCHWORK

To cope with the patch overload, I added all the patchwork patches into archived-v2.6.35 bundle when v2.6.35 got tagged:

http://patchwork.kernel.org/bundle/tmlind/archived-v2.6.35/?archive=both

However, at that point the patchwork instance on kernel.org was buggy, and I could not mark them all archived.

Anyways, I've marked them all archived now. This means they do not appear as new patches any longer, and patchwork.kernel.org is usable again for tracking what's already queued up.

I plan on archiving everything when a new major release comes out, maybe even after some -rc releases if necessary.

So the current list of patches we're working with for the upcoming merge window is:

http://patchwork.kernel.org/project/linux-omap/list/

Please everybody, check if your patch got archived, and if so, repost as needed against v2.6.36-rc4.

In general, if something got archived, please don't consider it rejected. It just means that you have to repost, fix and complain until the patch is ready and integrated :) The standard Linux way you know.

Regards,

Tony

#1 lore raw
Quoted 43 lines · Tony Lindgren

Hi all,

Here's some important info regarding posted patches and the upcoming merge window.

UPCOMING MERGE WINDOW

Just to remind everybody, we want to have our omap patches reviewed and queued into for-next by -rc6. That is less than two weeks from today.

If you have a larger set of patches, please set them up into a git branch after review for pulling. Please remember that anything touching arch/arm/*omap*/ must be also reviewed on the linux-arm-kernel list, so Cc that list too so I don't have to repost the patches before applying. Basically see the instructions here (server currently down?):

http://www.elinux.org/OMAP_patch_merging_process

POSTED PATCHES AND PATCHWORK

To cope with the patch overload, I added all the patchwork patches into archived-v2.6.35 bundle when v2.6.35 got tagged:

http://patchwork.kernel.org/bundle/tmlind/archived-v2.6.35/?archive=both

However, at that point the patchwork instance on kernel.org was buggy, and I could not mark them all archived.

Anyways, I've marked them all archived now. This means they do not appear as new patches any longer, and patchwork.kernel.org is usable again for tracking what's already queued up.

I plan on archiving everything when a new major release comes out, maybe even after some -rc releases if necessary.

So the current list of patches we're working with for the upcoming merge window is:

http://patchwork.kernel.org/project/linux-omap/list/

Quoted 8 lines

Please everybody, check if your patch got archived, and if so, repost as needed against v2.6.36-rc4.

In general, if something got archived, please don't consider it rejected. It just means that you have to repost, fix and complain until the patch is ready and integrated :) The standard Linux way you know.

Tony,

I posted this patch [1] a while ago fixing a bunch of compile warnings that show up with omap3_defconfig and omap_4430sdp_defconfig builds. I can't seem to locate it in patchworks; not sure how that happened.

Any chance you can pick this up (before more folks on LAKML start yelling about no-one caring for build warnings...)? Would you like me to post this again?

- Anand

[1] http://marc.info/?l=linux-omap&m=128212353619711&w=2

#2 lore raw
Quoted 5 lines · Gadiyar, Anand

I posted this patch [1] a while ago fixing a bunch of compile warnings that show up with omap3_defconfig and omap_4430sdp_defconfig builds. I can't seem to locate it in patchworks; not sure how that happened.

Quoted 7 lines

Any chance you can pick this up (before more folks on LAKML start yelling about no-one caring for build warnings...)? Would you like me to post this again?

- Anand

[1] http://marc.info/?l=linux-omap&m=128212353619711&w=2

Thanks, adding that with Felipe's ack. For some reason I could not find this in patchwork at all, I guess it must have been pretty broken at some point.

Anyways, for the other patches, please just repost so we'll have all the pending patches in one queue in patchwork.

Regards,

Tony