From: <Tudor.Ambarus@microchip.com>
To: <p.yadav@ti.com>
Cc: <michael@walle.cc>, <miquel.raynal@bootlin.com>, <richard@nod.at>,
<vigneshr@ti.com>, <michal.simek@xilinx.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<Nicolas.Ferre@microchip.com>
Subject: Re: [PATCH] mtd: spi-nor: Introduce templates for SPI NOR operations
Date: Wed, 20 Apr 2022 07:37:08 +0000 [thread overview]
Message-ID: <30d1f956-c196-6744-3dd7-7217c3298645@microchip.com> (raw)
In-Reply-To: <20220420063231.kdtppbpwceiyfocb@ti.com>
On 4/20/22 09:32, Pratyush Yadav wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 04/03/22 11:30AM, Tudor Ambarus wrote:
>> Clean the op declaration and hide the details of each op. With this it
>> results a cleanner, easier to read code. No functional change expected.
>>
>> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>
> I have not looked at the changes very closely but the idea sounds fine
> to me.
>
> Acked-by: Pratyush Yadav <p.yadav@ti.com>
>
thanks. Please note that I've resend this patch without any modification
at https://lore.kernel.org/linux-mtd/20220411091033.98754-10-tudor.ambarus@microchip.com/
You can mark this as superseeded and use that instead.
Cheers,
ta
prev parent reply other threads:[~2022-04-20 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 9:30 [PATCH] mtd: spi-nor: Introduce templates for SPI NOR operations Tudor Ambarus
2022-03-04 9:34 ` Tudor.Ambarus
2022-04-20 6:32 ` Pratyush Yadav
2022-04-20 7:37 ` Tudor.Ambarus [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=30d1f956-c196-6744-3dd7-7217c3298645@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=michal.simek@xilinx.com \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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).