From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Marek Vasut <marex@denx.de>, Richard Weinberger <richard@nod.at>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
David Woodhouse <dwmw2@infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PULL] mtd: nand: Fixes for 4.10-rc3
Date: Fri, 6 Jan 2017 09:05:56 +0100 [thread overview]
Message-ID: <20170106090556.5fa6a5a8@bbrezillon> (raw)
In-Reply-To: <20170105180710.GA138504@google.com>
On Thu, 5 Jan 2017 10:07:10 -0800
Brian Norris <computersforpeace@gmail.com> wrote:
> On Wed, Jan 04, 2017 at 09:15:57PM +0100, Boris Brezillon wrote:
> > Hi Brian,
> >
> > Here is a fixes PR for 4.10-rc3 (or -rc4 if it's already too late for
> > -rc3).
> >
> > The xway and oxnas fixes are fixing bugs introduced before 4.10-rc1. I
> > know fixes PRs are supposed to contain only fixes for bugs introduced by
> > code merged during the merge window, but I thought it would be good to
> > have them applied in this release.
>
> Actually, I thought all bugfixes are candidates (within reason of
> course) for post-rc1 merging, especially early rc's. I recall Linus
> saying things along the lines of "if it's a candidate for stable, then
> it's a candidate for an -rc" (i.e., don't wait until the next merge
> window).
Okay, good to know.
>
> These really aren't a big deal anyway.
>
> > Let me know if this is a problem, and I'll move them to my nand/next and
> > resend of PR.
>
> Pushed to linux-mtd.git. Thanks!
Thanks,
Boris
>
> Brian
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2017-01-06 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 20:15 [PULL] mtd: nand: Fixes for 4.10-rc3 Boris Brezillon
2017-01-05 18:07 ` Brian Norris
2017-01-06 8:05 ` Boris Brezillon [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=20170106090556.5fa6a5a8@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=richard@nod.at \
/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