stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: catalin.marinas@arm.com, will.deacon@arm.com,
	stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "arm64: fix building without CONFIG_UID16" has been added to the 3.10-stable tree
Date: Wed, 27 Jan 2016 09:53:26 -0800	[thread overview]
Message-ID: <20160127175326.GC22700@kroah.com> (raw)
In-Reply-To: <2570627.miLfsR1EUj@wuerfel>

On Wed, Jan 27, 2016 at 10:18:25AM +0100, Arnd Bergmann wrote:
> On Tuesday 26 January 2016 22:53:30 gregkh@linuxfoundation.org wrote:
> > 
> > This is a note to let you know that I've just added the patch titled
> > 
> >     arm64: fix building without CONFIG_UID16
> > 
> > to the 3.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:
> >      arm64-fix-building-without-config_uid16.patch
> > and it can be found in the queue-3.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.
> > 
> 
> Hi Greg,
> 
> This patch caused a regression on mn10300, so please also backport the one
> below to fix that. I have verified again that no other architectures had
> the same problem beside mn10300.

Now queued up, thanks.

greg k-h

      reply	other threads:[~2016-01-27 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  6:53 Patch "arm64: fix building without CONFIG_UID16" has been added to the 3.10-stable tree gregkh
2016-01-27  9:18 ` Arnd Bergmann
2016-01-27 17:53   ` 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=20160127175326.GC22700@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=will.deacon@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;
as well as URLs for NNTP newsgroup(s).