From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: About to tag 2.6.18-omap1 (Was: Pending September patches)
Date: Thu, 19 Oct 2006 17:10:56 +0300 [thread overview]
Message-ID: <20061019141054.GK9983@atomide.com> (raw)
In-Reply-To: <4523B6F8.3020800@gmail.com>
Hi,
I believe things are mostly working, except for the pending McBSP
without DSP compile issue. Most of the patches posted on this list
have been integrated, please notify if you feel something is still
missing. Also check that your patches got integrated properly.
Unless somebody knows of any showstoppers, I'll tag 2.6.18-omap1
tomorrow.
Below comments on Dirk's pending September patches list.
* Dirk Behme <dirk.behme@googlemail.com> [061004 16:28]:
> Hi,
>
> my list of pending OMAP patches for September 2006:
>
> 1. [PATCH] MTD patch, including the latest modifications an
> offical upgrades for MTD
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-September/007889.html
>
> Note: Is this still necessary or does 2.6.18 contain it
> automatically?
Skipped this one as only Ladis' driver patch was needed.
> 2.[PATCH 1/4] TSC2102 main SPI driver
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-September/007929.html
Pushed.
> 3. [PATCH 2/4] TSC2102 Touchscreen
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-September/007931.html
Pushed.
> Note: What's about "[PATCH 3/4] TSC2102 hwmon driver"?
Not needed any longer.
> 4. [PATCH 4/4] TSC2102 OMAP audio driver
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-September/007930.html
Pushed.
> 5. [PATCH] Request OMAP MMC Write-protect pin
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-September/007976.html
Not pushed, let's wait for a board-*.c solution.
> 6. LCD output from decompressor
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-September/007977.html
>
> Note: Should this be applied or only stay on the list for
> interested people?
Skipped.
> Please correct if I missed anything, if any of above patches
> are already applied or if any has comments I overlooked and
> needs resend. Are there any older patches pending?
Well there's Dave's RTC patches, but I think those should be tested
first.
Regards,
Tony
next prev parent reply other threads:[~2006-10-19 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 13:28 Pending September patches Dirk Behme
2006-10-04 15:55 ` andrzej zaborowski
2006-10-04 16:29 ` Help with LCD on OSK Sideleau, Scott R
2006-10-04 20:36 ` Ishigami, Tatsuya
2006-10-05 9:48 ` Sideleau, Scott R
2006-10-24 7:19 ` using __raw_read function Arnold
2006-10-25 18:04 ` Tony Lindgren
2006-10-26 2:29 ` Arnold
2006-10-04 18:22 ` Pending September patches Ladislav Michl
2006-10-19 13:54 ` Tony Lindgren
2006-10-19 14:10 ` Tony Lindgren [this message]
2006-10-19 14:49 ` About to tag 2.6.18-omap1 (Was: Pending September patches) Dirk Behme
2006-10-19 23:26 ` lamikr
2006-10-20 12:50 ` tony
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=20061019141054.GK9983@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