From: Dirk Behme <dirk.behme@googlemail.com>
To: linux-omap-open-source@linux.omap.com
Subject: Pending January patches
Date: Thu, 01 Feb 2007 17:52:42 +0100 [thread overview]
Message-ID: <45C21ADA.9090004@googlemail.com> (raw)
Hi,
my list of pending OMAP patches for January 2007:
Pending OMAP patches January 2007
---------------------------------
1. [PATCH] Basic N800 support
(onenand patch and mach-types hack)
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008958.html
(already from February:)
2. [PATCH] gpio-switch.c: use right flags for interrupts
http://linux.omap.com/pipermail/linux-omap-open-source/2007-February/008997.html
3. [PATCH] omap-hw: Fix build
http://linux.omap.com/pipermail/linux-omap-open-source/2007-February/008998.html
4. [PATCH] mtd/cmdlinepart.c: remove static declaration of
mtdpart_setup
http://linux.omap.com/pipermail/linux-omap-open-source/2007-February/008999.html
"Dave, can you have a look" patches ;)
--------------------------------------
1. [review] OMAP2 USB device DMA support
http://linux.omap.com/pipermail/linux-omap-open-source/2006-November/008342.html
2. [PATCH] MUSB HDRC: RMMOD fixing
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008853.html
3. [PATCH] ARM: OMAP: Fix warnings in musb_procfs.c
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008903.html
Open, do not apply yet
----------------------
I removed here "PalmZ71 MPUIO monitoring" and
"omap-alsa-aic23.c cleanup". See same section in
http://linux.omap.com/pipermail/linux-omap-open-source/2007-January/008778.html
for details.
As ususal, if you think that anything is wrong or missing.
Dirk
reply other threads:[~2007-02-01 16:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45C21ADA.9090004@googlemail.com \
--to=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