From: Sam Protsenko <semen.protsenko@linaro.org>
To: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: linux-rtc@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] rtc: s3c: S3C driver improvements
Date: Thu, 21 Oct 2021 23:22:53 +0300 [thread overview]
Message-ID: <20211021202256.28517-1-semen.protsenko@linaro.org> (raw)
While working on Exynos850 support (where this driver works fine in its
current state), I've stumbled upon some minor issue. This is the effort
to fix those.
* [PATCH 1/3]: moves S3C RTC driver to newer API usage
(no functional changes)
* [PATCH 2/3]: refactoring/cleanup (no functional changes)
* [PATCH 3/3]: adds time range, as [PATCH 1/3] made it possible
Changes in v2:
- Dropped "rtc: s3c: Fix RTC read on first boot" patch
- Switched the order for [PATCH 2/3] and [PATCH 3/3], so that the
refactoring patch can stay w/o functional changes w.r.t. previous
state
- See also changelist for each particular patch
Sam Protsenko (3):
rtc: s3c: Remove usage of devm_rtc_device_register()
rtc: s3c: Extract read/write IO into separate functions
rtc: s3c: Add time range
drivers/rtc/rtc-s3c.c | 106 ++++++++++++++++++++++++++----------------
1 file changed, 65 insertions(+), 41 deletions(-)
--
2.30.2
next reply other threads:[~2021-10-21 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 20:22 Sam Protsenko [this message]
2021-10-21 20:22 ` [PATCH v2 1/3] rtc: s3c: Remove usage of devm_rtc_device_register() Sam Protsenko
2021-10-21 20:22 ` [PATCH v2 2/3] rtc: s3c: Extract read/write IO into separate functions Sam Protsenko
2021-10-21 20:22 ` [PATCH v2 3/3] rtc: s3c: Add time range Sam Protsenko
2021-10-22 8:54 ` Krzysztof Kozlowski
2021-10-23 21:58 ` [PATCH v2 0/3] rtc: s3c: S3C driver improvements Alexandre Belloni
2021-11-11 17:05 ` Sam Protsenko
2021-11-12 22:19 ` Alexandre Belloni
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=20211021202256.28517-1-semen.protsenko@linaro.org \
--to=semen.protsenko@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-samsung-soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.