From: Greg KH <greg@kroah.com>
To: Mason <slash.tmp@free.fr>
Cc: stable@vger.kernel.org
Subject: Re: Requesting inclusion of mtd/nand patches in linux-3.14.y
Date: Tue, 28 Jul 2015 14:03:10 -0700 [thread overview]
Message-ID: <20150728210310.GA8427@kroah.com> (raw)
In-Reply-To: <55B7DFAE.3050802@free.fr>
On Tue, Jul 28, 2015 at 10:01:50PM +0200, Mason wrote:
> On 28/07/2015 19:34, Greg KH wrote:
>
> > On Tue, Jul 28, 2015 at 03:40:46PM +0200, Mason wrote:
> >
> >> This is my second time requesting inclusion of a patch,
> >> please point out any breach of protocol :-)
> >
> > I never saw your first request, where did you send that?
>
> Sorry Greg, my statement was ambiguous. I didn't mean that
> I had already proposed these patches for inclusion. I meant
> that today's request is only the second time I have gone
> through the process. I made a different request last week
> (which was accepted, thanks by the way).
>
> >> I have cherry-picked two mtd/nand patches on my local branch
> >> of linux-3.14.y and I realized that these fixes might benefit
> >> other users. (As far as I can tell, they landed in 3.15)
> >>
> >> bd9c6e99b582 mtd: nand: don't use read_buf for 8-bit ONFI transfers
> >> 60c3bc1fd6f1 mtd: nand: fix erroneous read_buf call in nand_write_page_raw_syndrome
> >
> > both now queued up, thanks.
>
> Thanks to you!
>
> When is 3.14.49 expected, roughly?
When it happens :)
next prev parent reply other threads:[~2015-07-28 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 13:40 Requesting inclusion of mtd/nand patches in linux-3.14.y Mason
2015-07-28 17:34 ` Greg KH
2015-07-28 20:01 ` Mason
2015-07-28 21:03 ` Greg KH [this message]
2015-08-25 21:43 ` Brian Norris
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=20150728210310.GA8427@kroah.com \
--to=greg@kroah.com \
--cc=slash.tmp@free.fr \
--cc=stable@vger.kernel.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).