From: George Stark <gnstark@sberdevices.ru>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: <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 v5 0/6] iio: adc: meson: add iio channels to read channel 7 mux inputs
Date: Thu, 13 Jul 2023 02:04:05 +0300 [thread overview]
Message-ID: <fe1b4eb7-e137-fe43-44cb-8de597fe00e4@sberdevices.ru> (raw)
In-Reply-To: <ZK7GCAgA1gljrxyl@smile.fi.intel.com>
Hello Andy
On 7/12/23 18:26, Andy Shevchenko wrote:
> On Tue, Jul 11, 2023 at 11:00:16PM +0300, George Stark wrote:
>> Changelog:
>
> I gave you a tag, any reason why you haven't applied it to your patches?
if you're talking about patch 6 commit message - yes, I missed the last
line in your letter, I'll fix it.
--
Best regards
George
next prev parent reply other threads:[~2023-07-12 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 20:00 George Stark
2023-07-11 20:00 ` [PATCH v5 1/6] iio: adc: meson: remove unused timestamp channel George Stark
2023-07-11 20:00 ` [PATCH v5 2/6] iio: adc: meson: move enums declaration before variables declaration George Stark
2023-07-11 20:00 ` [PATCH v5 3/6] iio: adc: meson: move meson_sar_adc_set_chan7_mux routine upper George Stark
2023-07-11 20:00 ` [PATCH v5 4/6] iio: adc: meson: add enum for iio channel numbers George Stark
2023-07-11 20:00 ` [PATCH v5 5/6] iio: adc: meson: add channel labels George Stark
2023-07-11 20:00 ` [PATCH v5 6/6] iio: adc: meson: support reading from channel 7 mux inputs George Stark
2023-07-12 15:26 ` [PATCH v5 0/6] iio: adc: meson: add iio channels to read " Andy Shevchenko
2023-07-12 23:04 ` George Stark [this message]
2023-07-13 12:08 ` Andy Shevchenko
2023-07-13 23:11 ` George Stark
2023-07-14 7:46 ` Andy Shevchenko
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=fe1b4eb7-e137-fe43-44cb-8de597fe00e4@sberdevices.ru \
--to=gnstark@sberdevices.ru \
--cc=andriy.shevchenko@linux.intel.com \
--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
all inboxes | Powered by JetHome®