From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Pending December (January) patches
Date: Tue, 9 Jan 2007 15:59:12 -0800 [thread overview]
Message-ID: <20070109235912.GX7384@atomide.com> (raw)
In-Reply-To: <459E6FE4.5030208@googlemail.com>
* 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
next prev parent reply other threads:[~2007-01-09 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 15:33 Pending December (January) patches Dirk Behme
2007-01-06 7:08 ` Komal Shah
2007-01-09 23:59 ` Tony Lindgren [this message]
2007-01-10 17:13 ` Dirk Behme
2007-01-10 19:17 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070109235912.GX7384@atomide.com \
--to=tony@atomide.com \
--cc=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox