From: Artem Bityutskiy <dedekind1@gmail.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: docg3 fix in-middle of blocks reads
Date: Fri, 13 Apr 2012 20:30:11 +0300 [thread overview]
Message-ID: <1334338211.13160.26.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <87r4vsg3ps.fsf@free.fr>
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
On Thu, 2012-04-12 at 21:17 +0200, Robert Jarzmik wrote:
> Hi Artem,
>
> Any chance this fix makes it into 3.4-rcN ?
Hmm, not sure about 3.4-rcN - it is up to him. But I'll try to ping him,
although I am going to be away for few weeks soon, so no guarantees.
Better ping him yourself.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-13 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 11:19 [PATCH] mtd: docg3 fix in-middle of blocks reads Robert Jarzmik
2012-04-12 19:17 ` Robert Jarzmik
2012-04-13 17:30 ` Artem Bityutskiy [this message]
2012-04-14 8:46 ` Robert Jarzmik
2012-04-13 17:30 ` Artem Bityutskiy
2012-05-15 15:04 ` David Woodhouse
2012-05-15 18:25 ` Robert Jarzmik
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=1334338211.13160.26.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=robert.jarzmik@free.fr \
/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