public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com
To: balrogg@gmail.com
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Pending August patches
Date: Tue, 5 Sep 2006 18:41:10 +0300	[thread overview]
Message-ID: <20060905154109.GE18073@atomide.com> (raw)
In-Reply-To: <20060904150433.GC8017@atomide.com>

OK, I've pushed Dirk's list except for the ones commented below.
Please check your patches got merged OK.

Regards,

Tony

1. [PATCH] ARM: OMAP: Remove warnings in DSP code
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007728.html

2. [PATCH] ARM: OMAP: Add GPIO API howto
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007733.html

3. [PATCH] Unmask omap-keypad interrupt on suspend
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007772.html

4. [PATCH] Add LCD backlight driver for OMAP
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007773.html

5. [PATCH] ARM: OMAP: Backlight configuration struct
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007774.html

6. [PATCH] ARM: OMAP: Register LCD backlight on PalmTE
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007775.html

7. [PATCH] ARM: OMAP: Add Amstrad Delta platform bits for framebuffer.
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007776.html

8. [PATCH 1/5] Change all omap15xx devices to use similar DMA handling than h6300 uses.
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007777.html

Already applied.

9. [PATCH 2/5] Removed double spinlocking with omap15xx devices.
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007778.html

Already applied.

10. [PATCH 3/5] Fix init warning in tsc2101 alsa driver.
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007779.html

11. [PATCH 4/5] tsc2101 mixer fixes.
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007780.html

12. [PATCH 5/5] Add gsm phone support for the mixer in tsc2101 alsa driver.
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007781.html

13. H3 alsa support
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007821.html

14. [PATCH] support printk-times by fixing sched_clock to be callable in early boot
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007828.html

Let's do this by implementing printk_clock() instead.

15. Re: [patch 2.6.17-rc4-omap-git] rtc-omap, rtc framework driver
or better: Handle wakeup irqs more correctly and completely
http://linux.omap.com/pipermail/linux-omap-open-source/2006-August/007853.html

Already applied.

  reply	other threads:[~2006-09-05 15:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01 16:15 Pending August patches Dirk Behme
2006-09-01 16:21 ` Zhang, Jian
2006-09-04 15:05   ` Dirk Behme
2006-09-01 16:50 ` Jonathan McDowell
2006-09-01 17:04 ` andrzej zaborowski
2006-09-04 15:04   ` Tony Lindgren
2006-09-05 15:41     ` tony [this message]
2006-09-11 23:26       ` andrzej zaborowski
2006-09-12 12:03         ` Tony Lindgren
  -- strict thread matches above, loose matches on Subject: below --
2007-09-01  5:17 Dirk Behme

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=20060905154109.GE18073@atomide.com \
    --to=tony@atomide.com \
    --cc=balrogg@gmail.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