From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ronald Monthero <debug.penguin32@gmail.com>
Cc: richard@nod.at, vigneshr@ti.com, heiko@sntech.de,
martin.blumenstingl@googlemail.com, paul@crapouillou.net,
robh@kernel.org, u.kleine-koenig@pengutronix.de,
AVKrasnov@sberdevices.ru, r.czerwinski@pengutronix.de,
jaimeliao.tw@gmail.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>
Subject: Re: [PATCH v2] mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response
Date: Mon, 13 Nov 2023 18:15:01 +0200 [thread overview]
Message-ID: <ZVJLhbvXSbmnEfwb@smile.fi.intel.com> (raw)
In-Reply-To: <20231113160751.620810-1-debug.penguin32@gmail.com>
On Tue, Nov 14, 2023 at 02:07:49AM +1000, Ronald Monthero wrote:
I'm not sure if it's a dup email of the previously sent v2. In any case I have
commented on v1 and v2, please consider addressing them.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-11-13 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231113131634.614467-1-debug.penguin32@gmail.com>
2023-11-13 15:53 ` [PATCH v2] mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response Ronald Monthero
2023-11-13 15:56 ` kernel test robot
2023-11-13 16:04 ` Andy Shevchenko
2023-11-13 16:11 ` Ronald Monthero
2023-11-13 17:32 ` [PATCH v3] " Ronald Monthero
2023-11-14 8:13 ` Miquel Raynal
2023-11-13 16:07 ` [PATCH v2] " Ronald Monthero
2023-11-13 16:15 ` Andy Shevchenko [this message]
2023-11-13 16:21 ` Ronald Monthero
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=ZVJLhbvXSbmnEfwb@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=AVKrasnov@sberdevices.ru \
--cc=debug.penguin32@gmail.com \
--cc=heiko@sntech.de \
--cc=jaimeliao.tw@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=miquel.raynal@bootlin.com \
--cc=nicolas.ferre@microchip.com \
--cc=paul@crapouillou.net \
--cc=philmd@linaro.org \
--cc=r.czerwinski@pengutronix.de \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--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