All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [APPLIED] [PATCH v3] omap: serial: fix non-empty uart fifo read abort
Date: Wed, 9 Dec 2009 08:28:00 -0800	[thread overview]
Message-ID: <20091209162800.GM24013@atomide.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB030ACBFA1C@dbde02.ent.ti.com>

* Gadiyar, Anand <gadiyar@ti.com> [091209 00:41]:
> Tony Lindgren wrote:
> > 
> > This patch has been applied to the linux-omap
> > by youw fwiendly patch wobot.
> > 
> > Branch in linux-omap: for-next-vol2
> > 
> 
> Tony,
> 
> A query on this for-next-vol2 branch:
> Is this branch going to be pushed in the current merge
> window, or is it for the -rc series?

What used to be for-next-vol2 is now the current for-next.
We should be able to get that merged too this merge window.

Regards,

Tony

> 
> 
> > PatchWorks
> > http://patchwork.kernel.org/patch/65022/
> 
> 
> With current Linus' tree + this patch, I can boot up on 3630.
> 
> Playing with the omap3_defconfig now, to see how many boards
> we can boot up with a single image :)
> 
> - Anand
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-12-09 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-05  0:20 [PATCH v3] omap: serial: fix non-empty uart fifo read abort Vikram Pandita
2009-12-07 22:23 ` [APPLIED] " Tony Lindgren
2009-12-09  8:42   ` Gadiyar, Anand
2009-12-09 14:17     ` Gadiyar, Anand
2009-12-09 16:29       ` Tony Lindgren
2009-12-09 16:28     ` 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=20091209162800.GM24013@atomide.com \
    --to=tony@atomide.com \
    --cc=gadiyar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.