From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [stable] [PATCH] MTD: pxa3xx_nand: fix nand detection issue
Date: Sat, 4 Jun 2011 09:45:25 +0200 [thread overview]
Message-ID: <BANLkTi=GEV3xfAZ+UphPPSG2hZavchiwPQ@mail.gmail.com> (raw)
In-Reply-To: <20110603223226.GC9161@kroah.com>
On Sat, Jun 4, 2011 at 12:32 AM, Greg KH <greg@kroah.com> wrote:
> On Fri, Jun 03, 2011 at 11:11:54PM +0800, Lei Wen wrote:
>> Tested-by: Daniel Mack <zonque@gmail.com>
>>
>> Also cc to MTD maillist and stable kernel.
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. ?Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
>
> </formletter>
Jup.
Lei - when you collect the patches for this driver to send them out,
make sure every one gets a "Cc: stable at kernel.org" line under the
S-o-b, so it can be picked automatically later on.
Just to be sure, I count four patches now:
- 1 from you regarding keep_config chip detection and DMA support
(which is *not* the one this thread refers to, you sent an amended
version to me privately, and it might make sense to split this patch
again)
- 1 from me for the blank page ECC issue
- 2 from Alex Lin (one for removal of unused variable, one plugs a memory leak)
Thanks,
Daniel
next prev parent reply other threads:[~2011-06-04 7:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 22:25 PXA3xx NAND controller support broken in 2.6.39 Daniel Mack
2011-05-20 4:20 ` [PATCH] MTD: pxa3xx_nand: fix nand detection issue Lei Wen
2011-06-03 15:11 ` Lei Wen
2011-06-03 22:32 ` [stable] " Greg KH
2011-06-04 7:45 ` Daniel Mack [this message]
2011-06-06 10:40 ` Artem Bityutskiy
[not found] ` <BANLkTim+Ndafbs6Cram6FpHUcJ1yxtXuRw@mail.gmail.com>
2011-05-20 6:38 ` PXA3xx NAND controller support broken in 2.6.39 Daniel Mack
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='BANLkTi=GEV3xfAZ+UphPPSG2hZavchiwPQ@mail.gmail.com' \
--to=zonque@gmail.com \
--cc=linux-arm-kernel@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).