linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Sørensen, Stefan" <Stefan.Sorensen@spectralink.com>
To: "computersforpeace@gmail.com" <computersforpeace@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: "hs@denx.de" <hs@denx.de>,
	"boris.brezillon@free-electrons.com"
	<boris.brezillon@free-electrons.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"fransklaver@gmail.com" <fransklaver@gmail.com>
Subject: Re: [for-4.4] mtd: nand: assign reasonable default name for NAND drivers
Date: Tue, 5 Jan 2016 15:28:14 +0000	[thread overview]
Message-ID: <1452007693.18078.3.camel@spectralink.com> (raw)
In-Reply-To: <1451934663-68925-1-git-send-email-computersforpeace@gmail.com>

Hi Brian,

On Mon, 2016-01-04 at 11:11 -0800, Brian Norris wrote:
> This patch is needed in additon to commit 472b444eef93 ("mtd: fix 
> cmdlinepart parser, early naming for auto-filled MTD") to fix Heiko's
> reported problem. At this point, I'm not sure if this should be
> targeted toward late 4.4 or for 4.5. It's a 4.4 regresssion, but a
> very small one. And I'm not sure if this will have wide enough
> impact that it should be given a longer time to be reviewed and
> tested. We can always send it to -stable later, if it's really
> needed.

I have boards that will not boot 4.4 without these two patches, so I
hope to see it go in to 4.4.1 (I guess it is too late for 4.4).

Regards, 
 Stefan

      parent reply	other threads:[~2016-01-05 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 19:11 [PATCH for-4.4] mtd: nand: assign reasonable default name for NAND drivers Brian Norris
2016-01-04 20:31 ` Boris Brezillon
2016-01-05 18:25   ` Brian Norris
2016-01-05  6:11 ` Heiko Schocher
2016-01-05 15:28 ` Sørensen, Stefan [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=1452007693.18078.3.camel@spectralink.com \
    --to=stefan.sorensen@spectralink.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=fransklaver@gmail.com \
    --cc=hs@denx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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 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).