From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-iio@vger.kernel.org, linux-amlogic@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, lars@metafoo.de, jic23@kernel.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [PATCH 0/3] iio: adc: meson-saradc: Three small improvements
Date: Sun, 18 Jul 2021 01:37:15 +0200 [thread overview]
Message-ID: <20210717233718.332267-1-martin.blumenstingl@googlemail.com> (raw)
Hello,
the first patch from this series saves a few CPU cycles on G12A, G12B
and SM1 SoCs. The other two patches are small whitespace cleanups.
In my opinion none of these patches are any real bugfix, which is why
I omitted the "Fixes" tag.
Martin Blumenstingl (3):
iio: adc: meson-saradc: Disable BL30 integration on G12A and newer
SoCs
iio: adc: meson-saradc: Add missing space between if and parenthesis
iio: adc: meson-saradc: Fix indentation of arguments after a
line-break
drivers/iio/adc/meson_saradc.c | 20 ++++++++++++++------
1 file changed, 14 insertions(+), 6 deletions(-)
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-07-17 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 23:37 Martin Blumenstingl [this message]
2021-07-17 23:37 ` [PATCH 1/3] iio: adc: meson-saradc: Disable BL30 integration on G12A and newer SoCs Martin Blumenstingl
2021-07-17 23:37 ` [PATCH 2/3] iio: adc: meson-saradc: Add missing space between if and parenthesis Martin Blumenstingl
2021-07-17 23:37 ` [PATCH 3/3] iio: adc: meson-saradc: Fix indentation of arguments after a line-break Martin Blumenstingl
2021-07-25 14:58 ` [PATCH 0/3] iio: adc: meson-saradc: Three small improvements 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=20210717233718.332267-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=jic23@kernel.org \
--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 \
/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