All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Wu <josh.wu@atmel.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Lior Amsalem <alior@marvell.com>,
	Tawfik Bayouk <tawfik@marvell.com>,
	Nadav Haklai <nadavh@marvell.com>,
	linux-mtd@lists.infradead.org,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: nand: reduce the warning noise when the ECC is too weak
Date: Mon, 21 Jul 2014 14:33:11 +0800	[thread overview]
Message-ID: <53CCB427.3090400@atmel.com> (raw)
In-Reply-To: <20140718165430.GY7537@ld-irv-0074>

Hi, Brian

On 7/19/2014 12:54 AM, Brian Norris wrote:
> On Fri, Jul 18, 2014 at 05:59:45PM +0800, Josh Wu wrote:
>> On 7/14/2014 1:22 PM, Brian Norris wrote:
>>> Pushed to linux-mtd.git, for 3.16 I think. Thanks!
>> Excuse me that to ask a question which is not related with the code.
>>
>> I find this fix is not in l2-mtd.git but only in linux-mtd.git. So I
>> wondering how the patch is merged in linux mainline and stable tree.
>>
>> Will the linux-mtd.git be merged in linux mainline and stable git
>> tree before v3.16 release? So the l2-mtd.git can rebase on the
>> merged tag.
> I'm still working out what the *best* process is, but linux-mtd.git is
> used as the official tree for pull requests to Linus, and I try hard to
> make sure it doesn't need rebased. l2-mtd.git has historically served a
> little more of a staging role, allowing rebases and is typically aimed
> for the next merge window.
>
> In this case, I specifically applied the patch to linux-mtd.git since I
> planned to (and did, already) send it to Linus for 3.16.
yes. I see the pull request.

> I will probably
> merge it back into l2-mtd.git soon, to keep the 'next' tree (l2-mtd.git)
> up-to-date.
>
> If you're looking to send patches for -next, please use l2-mtd.git (or
> even linux-next.git).
Thank you very much for the clear information. That's helpful.

>
> NB: linux-mtd.git and l2-mtd.git are both in linux-next. Perhaps
> l2-mtd.git should be in MAINTAINERS?
yes, I think so. The l2-mtd.git is used more often. It should be in 
MAINTAINERS as well.

>
> Regards,
> Brian
Best Regards,
Josh Wu

      reply	other threads:[~2014-07-21  6:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 13:16 [PATCH] mtd: nand: reduce the warning noise when the ECC is too weak Thomas Petazzoni
2014-07-14  5:22 ` Brian Norris
2014-07-18  9:59   ` Josh Wu
2014-07-18 16:54     ` Brian Norris
2014-07-21  6:33       ` Josh Wu [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=53CCB427.3090400@atmel.com \
    --to=josh.wu@atmel.com \
    --cc=alior@marvell.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nadavh@marvell.com \
    --cc=tawfik@marvell.com \
    --cc=thomas.petazzoni@free-electrons.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.