linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregkh@suse.de (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [ARM] pxa/cm-x300: fix ffuart registration
Date: Wed, 4 Aug 2010 10:06:57 -0700	[thread overview]
Message-ID: <20100804170657.GD28217@suse.de> (raw)
In-Reply-To: <AANLkTimiriUNY+NyOz5vwLzX05zUjxojbCaDgQrbw+1J@mail.gmail.com>

On Wed, Aug 04, 2010 at 11:37:33AM +0800, Eric Miao wrote:
> On Sun, Aug 1, 2010 at 8:10 PM, Igor Grinberg <grinberg@compulab.co.il> wrote:
> > On 07/20/10 13:54, Eric Miao wrote:
> >> On Tue, Jul 20, 2010 at 9:58 AM, Igor Grinberg <grinberg@compulab.co.il> wrote:
> >>
> >>> ffuart is available on cm-x300 only with pxa300.
> >>>
> >>> Signed-off-by: Igor Grinberg <grinberg@compulab.co.il>
> >>>
> >> Applied.
> >>
> >
> > I can see it neither in fix, nor in devel branches on your git.kernel.org.
> > Do you keep it locally?
> 
> Sorry it's in my local tree and missed the -rc phase. I'll push it within
> this merge window. Cc'ed stable and GregKH.
> 
> Greg,
> 
> Could you help pick this simple oneliner to -stable? Or we'd better
> wait a while until this appears in Linus' tree?

I am not allowed to take a patch in the stable tree unless it is already
in Linus's tree, sorry.

So I'll have to wait until then.  You do know about adding a:
	Cc: stable <stable@kernel.org>
to the signed-off-by area in the patch which will automatically notify
me when it goes into Linus's tree to be picked up for the next stable
releases, right?

thanks,

greg k-h

  reply	other threads:[~2010-08-04 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20  7:58 [PATCH] [ARM] pxa/cm-x300: fix ffuart registration Igor Grinberg
2010-07-20 10:54 ` Eric Miao
2010-08-01 12:10   ` Igor Grinberg
2010-08-04  3:37     ` Eric Miao
2010-08-04 17:06       ` Greg KH [this message]
2010-08-05  3:06         ` Eric Miao

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=20100804170657.GD28217@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).