From: Markus Elfring <Markus.Elfring@web.de>
To: "George Stark" <gnstark@sberdevices.ru>,
linux-iio@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Kevin Hilman" <khilman@baylibre.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Nuno Sá" <nuno.sa@analog.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel@sberdevices.ru
Subject: Re: [PATCH 1/3] iio: adc: meson: init channels 0,1 input muxes
Date: Sun, 16 Jul 2023 22:24:08 +0200 [thread overview]
Message-ID: <eeb9465a-da71-c182-22df-77f0e5ed0c39@web.de> (raw)
In-Reply-To: <20230715110654.6035-2-gnstark@sberdevices.ru>
> Set up input channels 0,1 muxes in the same way as for the channels 2-7
> later in the code.
Can a wording variant like “Set input channels “0,1 muxes” up …”
be a bit nicer?
(Is there a need to adjust any comments in the source code accordingly?)
Would you like to avoid empty descriptions according to addresses
in applied recipient lists?
Regards,
Markus
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-07-16 20:25 UTC|newest]
Thread overview: 11+ 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-16 20:24 ` Markus Elfring [this message]
2023-07-15 11:05 ` [PATCH v1 2/3] iio: adc: meson: init internal continuous ring counter George Stark
2023-07-16 20:36 ` [PATCH " Markus Elfring
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
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=eeb9465a-da71-c182-22df-77f0e5ed0c39@web.de \
--to=markus.elfring@web.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gnstark@sberdevices.ru \
--cc=jbrunet@baylibre.com \
--cc=jic23@kernel.org \
--cc=kernel-janitors@vger.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