From: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
"Brian Norris" <computersforpeace@gmail.com>,
"Marek Vašut" <marek.vasut@gmail.com>,
cyrille.pitchen@wedev4u.fr, linux-mtd@lists.infradead.org,
"open list" <linux-kernel@vger.kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>
Subject: Re: [RFC] NAND: Optimize NAND_ECC_HW_OOB_FIRST read
Date: Tue, 31 Oct 2017 21:50:32 +0530 [thread overview]
Message-ID: <CANc+2y4aLytChOjkMXBu92O+pfiZPP3AwXgu4XF1EkBsULv+2A@mail.gmail.com> (raw)
In-Reply-To: <CANc+2y5QWNSRf_-oOuU8TYbyVHYrbPqK8+gO=Y56-MMaJp+nZQ@mail.gmail.com>
Hi Boris,
On 30 October 2017 at 19:04, PrasannaKumar Muralidharan
<prasannatsmkumar@gmail.com> wrote:
> Hi Boris,
>
> On 30 October 2017 at 18:33, Boris Brezillon
> <boris.brezillon@free-electrons.com> wrote:
>>
>> Yep, it makes sense to have that one applied too, but this is pretty
>> much the same problem: it will conflict with the ->exec_op() rework.
>
> True. I did realise that.
>
>> Can you please send it to the ML so I can track it in patchwork and
>
> Sure.
I could not get that patch compiled yet. I will revisit it next week
and send the patch.
Regards,
PrasannaKumar
next prev parent reply other threads:[~2017-10-31 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 7:43 [RFC] NAND: Optimize NAND_ECC_HW_OOB_FIRST read PrasannaKumar Muralidharan
2017-10-30 8:34 ` Boris Brezillon
2017-10-30 12:47 ` PrasannaKumar Muralidharan
2017-10-30 13:03 ` Boris Brezillon
2017-10-30 13:34 ` PrasannaKumar Muralidharan
2017-10-31 16:20 ` PrasannaKumar Muralidharan [this message]
2018-01-27 7:42 ` PrasannaKumar Muralidharan
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=CANc+2y4aLytChOjkMXBu92O+pfiZPP3AwXgu4XF1EkBsULv+2A@mail.gmail.com \
--to=prasannatsmkumar@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.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 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).