From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Sean Young <sean@mess.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
linux-pwm@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] pwm: bcm2835: Remove duplicate call to clk_rate_exclusive_put()
Date: Sat, 13 Jan 2024 09:36:12 +0100 [thread overview]
Message-ID: <2nropn2obzpwedkbm5vtgdgvhjg26jici4wxawvn2xmk2cypzy@z7h54tcqurte> (raw)
In-Reply-To: <sbcslehlbdhjggyb4thughrzuzjrbc3knbh3ulfhhi6mcrvayd@rbheyjouom6d>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
Hello,
On Wed, Jan 03, 2024 at 01:28:25PM +0100, Uwe Kleine-König wrote:
> this patch should be added to your for-next branch and then your PR for
> the next merge window.
This was missed for the pwm/for-6.8-rc1 PR. I added it to my for-next
branch at
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/for-next
now with the intention to send it for inclusion in 6.8-rc after being in
next for a few days.
> Also "pwm: linux/pwm.h: fix Excess kernel-doc description warning"
> (Message-Id: 20231223050621.13994-1-rdunlap@infradead.org) should be
> added IMHO.
This one was already cared for.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-01-13 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 13:13 [PATCH v2] pwm: bcm2835: Remove duplicate call to clk_rate_exclusive_put() Sean Young
2023-12-26 10:44 ` Florian Fainelli
2024-01-03 12:28 ` Uwe Kleine-König
2024-01-13 8:36 ` Uwe Kleine-König [this message]
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=2nropn2obzpwedkbm5vtgdgvhjg26jici4wxawvn2xmk2cypzy@z7h54tcqurte \
--to=u.kleine-koenig@pengutronix.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=sean@mess.org \
--cc=thierry.reding@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).