Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: aleksey.makarov@linaro.org, jslaby@suse.com,
	linux@armlinux.org.uk, peter@hurleysoftware.com,
	stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "tty: serial: pl011: add ttyAMA for matching pl011 console" has been added to the 4.10-stable tree
Date: Tue, 9 May 2017 14:10:32 +0200	[thread overview]
Message-ID: <20170509121032.GA20590@kroah.com> (raw)
In-Reply-To: <20170509112134.GA7046@kroah.com>

On Tue, May 09, 2017 at 01:21:34PM +0200, Greg KH wrote:
> On Tue, May 09, 2017 at 10:32:13AM +0100, Sudeep Holla wrote:
> > Hi Greg,
> > 
> > On 09/05/17 10:21, gregkh@linuxfoundation.org wrote:
> > > 
> > > This is a note to let you know that I've just added the patch titled
> > > 
> > >     tty: serial: pl011: add ttyAMA for matching pl011 console
> > > 
> > > to the 4.10-stable tree which can be found at:
> > >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > > 
> > > The filename of the patch is:
> > >      tty-serial-pl011-add-ttyama-for-matching-pl011-console.patch
> > > and it can be found in the queue-4.10 subdirectory.
> > > 
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> > > 
> > > 
> > > From aea9a80ba98a0c9b4de88850260e9fbdcc98360b Mon Sep 17 00:00:00 2001
> > > From: Sudeep Holla <sudeep.holla@arm.com>
> > > Date: Wed, 1 Feb 2017 15:46:38 +0000
> > > Subject: tty: serial: pl011: add ttyAMA for matching pl011 console
> > > 
> > > From: Sudeep Holla <sudeep.holla@arm.com>
> > > 
> > > commit aea9a80ba98a0c9b4de88850260e9fbdcc98360b upstream.
> > > 
> > 
> > I am not sure on the procedure for stable tree, but thought I will let
> > you know the information on this.
> > 
> > Commit b767ad726c2a ("Revert "tty: serial: pl011: add ttyAMA for
> > matching pl011 console"") reverted the above commit(commit in $subject)
> > 
> > It was properly fixed in the following upstream commits:
> > 
> > cf39bf58afda ("printk: fix double printing with earlycon")
> > ad86ee2b8a47 ("printk: rename selected_console -> preferred_console")
> > b077bafa2f38 ("printk: fix name/type/scope of preferred_console var")
> > 
> > Sorry for the trouble.
> 
> No trouble at all, thanks for letting me know.  I've dropped the tty
> patch now and will look at adding the printk ones instead.

Hm, as the printk patches will be in 4.12-rc1, I'll wait for that to be
out before considering them.

thanks,

greg k-h

      reply	other threads:[~2017-05-09 12:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09  9:21 Patch "tty: serial: pl011: add ttyAMA for matching pl011 console" has been added to the 4.10-stable tree gregkh
2017-05-09  9:32 ` Sudeep Holla
2017-05-09 11:21   ` Greg KH
2017-05-09 12:10     ` Greg KH [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=20170509121032.GA20590@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aleksey.makarov@linaro.org \
    --cc=jslaby@suse.com \
    --cc=linux@armlinux.org.uk \
    --cc=peter@hurleysoftware.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sudeep.holla@arm.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