From: Brian Norris <computersforpeace@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Vladimir Zapolskiy <vz@mleia.com>,
Richard Weinberger <richard@nod.at>,
Sylvain Lemieux <slemieux.tyco@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mtd: nand: lpc32xx: fix invalid error handling of a requested irq
Date: Thu, 5 Jan 2017 09:58:51 -0800 [thread overview]
Message-ID: <20170105175851.GC50438@google.com> (raw)
In-Reply-To: <20170103114746.141d7d7d@bbrezillon>
On Tue, Jan 03, 2017 at 11:47:46AM +0100, Boris Brezillon wrote:
> On Tue, 3 Jan 2017 12:16:26 +0200
> Vladimir Zapolskiy <vz@mleia.com> wrote:
> > On 01/03/2017 11:12 AM, Boris Brezillon wrote:
> > > Do you need to backport this fix to stable releases? If that's the
> > > case, I'll add the Cc: stable tag when applying.
> >
> > that will be great if you can add
> >
> > Cc: stable@kernel.org # v4.7+
> >
> > Please feel free to add also the tag
> >
> > Fixes: 8cb17b5ed017 ("irqchip: Add LPC32xx interrupt controller driver")
>
> Applied to nand/next (this patch will appear in 4.11).
For next time, checkpatch noticed that you got the stable address wrong:
ERROR:STABLE_ADDRESS: The 'stable' address should be 'stable@vger.kernel.org'
#17: Cc: stable@kernel.org # v4.7+
Brian
WARNING: multiple messages have this Message-ID (diff)
From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: nand: lpc32xx: fix invalid error handling of a requested irq
Date: Thu, 5 Jan 2017 09:58:51 -0800 [thread overview]
Message-ID: <20170105175851.GC50438@google.com> (raw)
In-Reply-To: <20170103114746.141d7d7d@bbrezillon>
On Tue, Jan 03, 2017 at 11:47:46AM +0100, Boris Brezillon wrote:
> On Tue, 3 Jan 2017 12:16:26 +0200
> Vladimir Zapolskiy <vz@mleia.com> wrote:
> > On 01/03/2017 11:12 AM, Boris Brezillon wrote:
> > > Do you need to backport this fix to stable releases? If that's the
> > > case, I'll add the Cc: stable tag when applying.
> >
> > that will be great if you can add
> >
> > Cc: stable at kernel.org # v4.7+
> >
> > Please feel free to add also the tag
> >
> > Fixes: 8cb17b5ed017 ("irqchip: Add LPC32xx interrupt controller driver")
>
> Applied to nand/next (this patch will appear in 4.11).
For next time, checkpatch noticed that you got the stable address wrong:
ERROR:STABLE_ADDRESS: The 'stable' address should be 'stable at vger.kernel.org'
#17: Cc: stable at kernel.org # v4.7+
Brian
next prev parent reply other threads:[~2017-01-05 17:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 1:47 [PATCH] mtd: nand: lpc32xx: fix invalid error handling of a requested irq Vladimir Zapolskiy
2016-12-05 1:47 ` Vladimir Zapolskiy
2016-12-07 18:09 ` Sylvain Lemieux
2016-12-07 18:09 ` Sylvain Lemieux
2017-01-03 9:12 ` Boris Brezillon
2017-01-03 9:12 ` Boris Brezillon
2017-01-03 10:16 ` Vladimir Zapolskiy
2017-01-03 10:16 ` Vladimir Zapolskiy
2017-01-03 10:47 ` Boris Brezillon
2017-01-03 10:47 ` Boris Brezillon
2017-01-05 17:58 ` Brian Norris [this message]
2017-01-05 17:58 ` Brian Norris
2017-01-05 18:19 ` Vladimir Zapolskiy
2017-01-05 18:19 ` Vladimir Zapolskiy
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=20170105175851.GC50438@google.com \
--to=computersforpeace@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=slemieux.tyco@gmail.com \
--cc=vz@mleia.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 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.