From: "Maxime Ripard" <mripard@kernel.org>
To: "Mans Rullgard" <mans@mansr.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
"Chen-Yu Tsai" <wens@csie.org>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Samuel Holland" <samuel@sholland.org>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH 0/3] clocksource: sun5i: clean up and convert to platform driver
Date: Mon, 03 Jul 2023 08:33:11 +0000 [thread overview]
Message-ID: <b24c27d0d32ca8ca4c58773e2d45b8a1.mripard@kernel.org> (raw)
In-Reply-To: <20230630201800.16501-1-mans@mansr.com>
On Fri, 30 Jun 2023 21:01:25 +0100, Mans Rullgard wrote:
> The first two of these patches remove a bunch of duplicated code/data in
> the sun5i hstimer driver. To keep the diff clearer, the first patch
> introduces an otherwise pointless struct which is then removed in the
> second.
>
>
> [ ... ]
Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-07-03 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 20:01 [PATCH 0/3] clocksource: sun5i: clean up and convert to platform driver Mans Rullgard
2023-06-30 20:01 ` [PATCH 1/3] clocksource: sun5i: remove duplication of code and data Mans Rullgard
2023-07-11 19:03 ` Jernej Škrabec
2023-06-30 20:01 ` [PATCH 2/3] clocksource: sun5i: remove pointless struct Mans Rullgard
2023-07-11 19:03 ` Jernej Škrabec
2023-06-30 20:01 ` [PATCH 3/3] clocksource: sun5i: convert to platform device driver Mans Rullgard
2023-07-11 19:07 ` Jernej Škrabec
2023-07-03 8:33 ` Maxime Ripard [this message]
2023-08-18 10:16 ` [PATCH 0/3] clocksource: sun5i: clean up and convert to platform driver Daniel Lezcano
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=b24c27d0d32ca8ca4c58773e2d45b8a1.mripard@kernel.org \
--to=mripard@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mans@mansr.com \
--cc=samuel@sholland.org \
--cc=tglx@linutronix.de \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).