From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Brian Norris <computersforpeace@gmail.com>
Cc: "Yang, Wenyou" <Wenyou.Yang@atmel.com>,
"romain.izard.pro@gmail.com" <romain.izard.pro@gmail.com>,
"boris.brezillon@free-electrons.com"
<boris.brezillon@free-electrons.com>,
"robh@kernel.org" <robh@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] mtd: atmel_nand: Support variable RB_EDGE interrupts" failed to apply to 4.6-stable tree
Date: Mon, 6 Jun 2016 13:46:29 -0700 [thread overview]
Message-ID: <20160606204629.GA26970@kroah.com> (raw)
In-Reply-To: <20160606202327.GA77765@google.com>
On Mon, Jun 06, 2016 at 01:23:27PM -0700, Brian Norris wrote:
> On Mon, Jun 06, 2016 at 07:57:56AM +0000, Yang, Wenyou wrote:
> > > -----Original Message-----
> > > From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]
> > > Sent: 2016年6月5日 5:58
> > > To: romain.izard.pro@gmail.com; Yang, Wenyou <Wenyou.Yang@atmel.com>;
> > > boris.brezillon@free-electrons.com; computersforpeace@gmail.com;
> > > robh@kernel.org; Yang, Wenyou <Wenyou.Yang@atmel.com>
> > > Cc: stable@vger.kernel.org
> > > Subject: FAILED: patch "[PATCH] mtd: atmel_nand: Support variable RB_EDGE
> > > interrupts" failed to apply to 4.6-stable tree
> > >
> > >
> > > The patch below does not apply to the 4.6-stable tree.
> > > If someone wants it applied there, or to any other stable or longterm tree, then
> > > please email the backport, including the original git commit id to
> > > <stable@vger.kernel.org>.
> >
> > This patch is unneeded.
> > It has been reverted by the commit 53b74ed2d0b4 ("Revert "mtd: atmel_nand: Support variable RB_EDGE interrupts"").
> >
> > Please don't apply this one.
> >
> > >
> > > thanks,
> > >
> > > greg k-h
> > >
> > > ------------------ original commit in Linus's tree ------------------
> > >
> > > From 5ddc7bd43ccc77173f149483fa27a0b8f85e09e5 Mon Sep 17 00:00:00 2001
> > > From: Romain Izard <romain.izard.pro@gmail.com>
> > > Date: Wed, 10 Feb 2016 10:56:23 +0100
> > > Subject: [PATCH] mtd: atmel_nand: Support variable RB_EDGE interrupts
>
> Why is commit 5ddc7bd43ccc77173f149483fa27a0b8f85e09e5 even showing up
> here? If this was automated, then that seems like a bug in the -stable
> scripts.
In looking at this, I have NO idea how this even was attempted to be
added to the stable tree. Maybe it was a cut-and-paste error on my part
when I sent out the "did not apply" message? But why would I even have
this commit open in a window?
I really don't know, sorry, I can't see any email from anyone asking me
to apply it, nor any script that actually picked it up to try to apply
it (nothing is ever auto-applied, I have to approve each commit after
reviewing them.)
So, sorry for the noise, I was dealing with a few hundred patches and
something messed up here, sorry.
greg k-h
prev parent reply other threads:[~2016-06-06 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 21:57 FAILED: patch "[PATCH] mtd: atmel_nand: Support variable RB_EDGE interrupts" failed to apply to 4.6-stable tree gregkh
2016-06-06 7:57 ` Yang, Wenyou
2016-06-06 20:23 ` Brian Norris
2016-06-06 20:46 ` gregkh [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=20160606204629.GA26970@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Wenyou.Yang@atmel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=robh@kernel.org \
--cc=romain.izard.pro@gmail.com \
--cc=stable@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.