public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Subject: Re: [APPLIED] [PATCH 3/3] OMAP: dmtimer: enable all timers to be wakeup events
Date: Tue, 7 Apr 2009 11:04:47 -0700	[thread overview]
Message-ID: <20090407180447.GC23823@atomide.com> (raw)
In-Reply-To: <notify-1239126497@atomide.com>

* Tony Lindgren <tony@atomide.com> [090407 10:49]:
> This patch has been applied to the linux-omap
> by youw fwiendly patch wobot.
> 
> Initial commit ID (Likely to change): 7287a91be3de9ee00f8da7c07f19b368fd0969ae
> 
> PatchWorks
> http://patchwork.kernel.org/patch/16349/
> 
> Git
> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=7287a91be3de9ee00f8da7c07f19b368fd0969ae

Well let's change the order of these patches, if you can sink #3
before #3 as we discussed on the phone. This way if adding the
gpt 12 support for Beagle is considered too intrusive, it's
easier to drop from omap-fixes and move to for-next instead.

So dropping all three until you have the updated series available.

Thanks,

Tony

      reply	other threads:[~2009-04-07 18:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04 20:54 [PATCH 0/3] OMAP2/3: GPTIMER12 fixes Paul Walmsley
2009-04-04 20:54 ` [PATCH 1/3] OMAP3 GPTIMER: fix GPTIMER12 IRQ Paul Walmsley
2009-04-07 17:46   ` [APPLIED] " Tony Lindgren
2009-04-04 20:54 ` [PATCH 2/3] OMAP2/3 GPTIMER: allow system tick GPTIMER to be changed in board-*.c files Paul Walmsley
2009-04-07 17:47   ` [APPLIED] [PATCH 2/3] OMAP2/3 GPTIMER: allow system tick GPTIMER to be changed Tony Lindgren
2009-04-04 20:54 ` [PATCH 3/3] OMAP: dmtimer: enable all timers to be wakeup events Paul Walmsley
2009-04-07 17:48   ` [APPLIED] " Tony Lindgren
2009-04-07 18:04     ` Tony Lindgren [this message]

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=20090407180447.GC23823@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    /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