Pending December (January) patches

Pending December (January) patches

[Dirk Behme]

Hi,

I had some problems with mail to the list, so instead of a 
pending december patches mail an update which includes 
already our patches from yesterday. Yes, it's clear that 
they can't be applied yet ;)

December 2006 pending patches
-----------------------------

1. [RFC][PATCH] Update MMC response types
http://linux.omap.com/pipermail/linux-omap-open-source/2006-December/008643.html

Note: Is this already merged anywhere else? Or should this 
be applied against OMAP git?


Open, do not apply yet (see list archive for details)
-----------------------------------------------------

1. [PATCH] ARM: OMAP: PalmZ71 MPUIO monitoring
http://linux.omap.com/pipermail/linux-omap-open-source/2006-November/008373.html

- Does not apply cleanly, please update

2. [PATCH] ARM: OMAP: omap-alsa-aic23.c cleanup. No code change
http://linux.omap.com/pipermail/linux-omap-open-source/2006-December/008572.html

- Does not apply cleanly, please update

-> Note: Will we get updates for these, or should I remove 
them from my list?


  Pending OMAP patches January 2007
---------------------------------

1. [PATCH] ARM: OMAP: Fix missing workqueue include in 
board-h2.c
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008757.html

2. [PATCH] ARM: OMAP: Update omap_h2_1610_defconfig
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008760.html

3. [PATCH] ARM: OMAP: Workqueue changes for board-h4.c
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008761.html

4. [PATCH] ARM: OMAP: Add missing includes to board-nokia770
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008762.html

5. [PATCH] ARM: OMAP: Add missing include to dsp/mblog.c
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008763.html

6. [PATCH] ARM: OMAP: Workqueue changes for tahvo-usb
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008764.html

7. [PATCH] ARM: OMAP: Workqueue changes for retu-rtc
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008765.html

8. [PATCH] ARM: OMAP: Fix section mismatch warnings in omap-rng
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008769.html

9. [PATCH] ARM: OMAP: Make board-palmz71 compile again
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008770.html

10. [PATCH] ARM: OMAP: Fix warnings in lcd_palmz71
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008771.html

11. innovator_ps2 broken
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008772.html

12. [PATCH] Make omap-ir build with workqueue changes.
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008773.html

13. [PATCH] Make omap_bl build again after API change.
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008776.html

As ususal, correct if anything is wrong or missing, 
especially from december or older. Thanks to Tony for 
merging all of our patches!

Dirk

Re: Pending December (January) patches

[Komal Shah]

On 1/5/07, Dirk Behme <dirk.behme@googlemail.com> wrote:
> Hi,
>
> I had some problems with mail to the list, so instead of a
> pending december patches mail an update which includes
> already our patches from yesterday. Yes, it's clear that
> they can't be applied yet ;)
>
> December 2006 pending patches
> -----------------------------
>
> 1. [RFC][PATCH] Update MMC response types
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-December/008643.html
>
> Note: Is this already merged anywhere else? Or should this
> be applied against OMAP git?
>
>
> Open, do not apply yet (see list archive for details)
> -----------------------------------------------------
>
> 1. [PATCH] ARM: OMAP: PalmZ71 MPUIO monitoring
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-November/008373.html
>
> - Does not apply cleanly, please update
>
> 2. [PATCH] ARM: OMAP: omap-alsa-aic23.c cleanup. No code change
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-December/008572.html
>
> - Does not apply cleanly, please update
>
> -> Note: Will we get updates for these, or should I remove
> them from my list?
>

You can remove this from list. I will re-submit this patch once I come
back from 2wks vacation starting from Monday :)

-- 
---Komal Shah
http://komalshah.blogspot.com

Re: Pending December (January) patches

[Tony Lindgren]

* Dirk Behme <dirk.behme@googlemail.com> [070105 07:36]:
> Hi,
> 
> I had some problems with mail to the list, so instead of a 
> pending december patches mail an update which includes 
> already our patches from yesterday. Yes, it's clear that 
> they can't be applied yet ;)
> 
> December 2006 pending patches
> -----------------------------
> 
> 1. [RFC][PATCH] Update MMC response types
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-December/008643.html
> 
> Note: Is this already merged anywhere else? Or should this 
> be applied against OMAP git?

I've applied this to omap tree, should go also into Pierre's queue.

<snip>
 
>  Pending OMAP patches January 2007
> ---------------------------------
> 
> 1. [PATCH] ARM: OMAP: Fix missing workqueue include in 
> board-h2.c
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008757.html
> 
> 2. [PATCH] ARM: OMAP: Update omap_h2_1610_defconfig
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008760.html
> 
> 3. [PATCH] ARM: OMAP: Workqueue changes for board-h4.c
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008761.html
> 
> 4. [PATCH] ARM: OMAP: Add missing includes to board-nokia770
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008762.html
> 
> 5. [PATCH] ARM: OMAP: Add missing include to dsp/mblog.c
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008763.html
> 
> 6. [PATCH] ARM: OMAP: Workqueue changes for tahvo-usb
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008764.html
> 
> 7. [PATCH] ARM: OMAP: Workqueue changes for retu-rtc
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008765.html
> 
> 8. [PATCH] ARM: OMAP: Fix section mismatch warnings in omap-rng
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008769.html
> 
> 9. [PATCH] ARM: OMAP: Make board-palmz71 compile again
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008770.html
> 
> 10. [PATCH] ARM: OMAP: Fix warnings in lcd_palmz71
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008771.html
> 
> 11. innovator_ps2 broken
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008772.html
> 
> 12. [PATCH] Make omap-ir build with workqueue changes.
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008773.html
> 
> 13. [PATCH] Make omap_bl build again after API change.
> http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008776.html

These should be applied now, everybody please check your patches got
applied OK.

Regards,

Tony

Re: Pending December (January) patches

[Dirk Behme]

Tony Lindgren wrote:
> These should be applied now, everybody please check your patches got
> applied OK.

Except the two patches which need update our pending patches 
list is now empty :) Thanks!

What do you think about preparing stuff for 2.6.21 upstream 
merge window now? 2.6.20-rc4 is there and it looks like this 
is a calmer release, maybe 2.6.20 is coming in time.

I think frist we should remove our old stuff from RMKs patch 
tracking system. It is still in incoming state [1]. Then 
send the updates so RMK can early comment on it. With some 
luck we hit the 2.6.21-rc1 window.

Tony: Not sure about your current workload, maybe people can 
help?

All: Opinions?

Cheers

Dirk

[1] 
http://www.arm.linux.org.uk/developer/patches/section.php?section=0

Re: Pending December (January) patches

[Tony Lindgren]

Hi,

* Dirk Behme <dirk.behme@googlemail.com> [070110 09:14]:
> Tony Lindgren wrote:
> >These should be applied now, everybody please check your patches got
> >applied OK.
> 
> Except the two patches which need update our pending patches 
> list is now empty :) Thanks!

:)
 
> What do you think about preparing stuff for 2.6.21 upstream 
> merge window now? 2.6.20-rc4 is there and it looks like this 
> is a calmer release, maybe 2.6.20 is coming in time.

Yes, I'll update that probably next week so we'll be ready well
ahead.
 
> I think frist we should remove our old stuff from RMKs patch 
> tracking system. It is still in incoming state [1]. Then 
> send the updates so RMK can early comment on it. With some 
> luck we hit the 2.6.21-rc1 window.

I agree. If we have conflicting patches, it may cause some delays
getting the big patch set applied. I just marked the previous core
omap patches as superceded.

Does anybody have bug fixes that should go to mainline before
the big merge? If there aren't any urgent ones, I suggest we
wait for 2.6.20 to make the big merge easier.
 
> Tony: Not sure about your current workload, maybe people can 
> help?
>
> All: Opinions?

I've scheduled some time for this and the patch queue is now pretty
easy to update. Also I've scripted out some parts :) So I think we're
in good shape for sending out the core omap patches.

Where people can help is picking an individual driver subsystem to
clean up for sending it upstream.

Imre will be sending out the framebuffer patches when he has a chance.
But at least sound and v4l driver code should be cleaned up and
sent upstream.

Anybody interested in working on merging audio and/or v4l?

Regards,

Tony
 

> [1] 
> http://www.arm.linux.org.uk/developer/patches/section.php?section=0