From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: George Stark <gnstark@sberdevices.ru>
Cc: Jonathan Cameron <jic23@kernel.org>,
lars@metafoo.de, neil.armstrong@linaro.org, khilman@baylibre.com,
jbrunet@baylibre.com, martin.blumenstingl@googlemail.com,
nuno.sa@analog.com, linux-iio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org,
kernel@sberdevices.ru
Subject: Re: [PATCH v1 0/3] iio: adc: meson: tune init sequence
Date: Mon, 17 Jul 2023 13:01:09 +0300 [thread overview]
Message-ID: <ZLURZWPkmP6aKDOZ@smile.fi.intel.com> (raw)
In-Reply-To: <a172c764-1eef-835f-f237-8f78b4c6e877@sberdevices.ru>
On Mon, Jul 17, 2023 at 12:41:29PM +0300, George Stark wrote:
> On 7/16/23 19:11, Jonathan Cameron wrote:
> > On Sat, 15 Jul 2023 14:05:57 +0300
> > George Stark <gnstark@sberdevices.ru> wrote:
...
> > These look fine to me, but I'd like them to sit on list a little while
> > on off chance anyone else has feedback on them.
>
> I understand. I'd resend the patches in a week or more if there's no
> feedback.
There is no need to resend as long as they are available via lore.kernel.org
mail archives.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-07-17 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 11:05 [PATCH v1 0/3] iio: adc: meson: tune init sequence George Stark
2023-07-15 11:05 ` [PATCH v1 1/3] iio: adc: meson: init channels 0,1 input muxes George Stark
2023-07-15 11:05 ` [PATCH v1 2/3] iio: adc: meson: init internal continuous ring counter George Stark
2023-07-15 11:06 ` [PATCH v1 3/3] iio: adc: meson: init voltage control bits George Stark
2023-07-16 16:11 ` [PATCH v1 0/3] iio: adc: meson: tune init sequence Jonathan Cameron
2023-07-17 9:41 ` George Stark
2023-07-17 10:01 ` Andy Shevchenko [this message]
2023-07-18 9:41 ` Jonathan Cameron
2023-07-22 16:59 ` Jonathan Cameron
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=ZLURZWPkmP6aKDOZ@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gnstark@sberdevices.ru \
--cc=jbrunet@baylibre.com \
--cc=jic23@kernel.org \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=nuno.sa@analog.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