From: Randy Dunlap <rd.dunlab@gmail.com>
To: Biju Das <biju.das.jz@bp.renesas.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Thierry Reding" <thierry.reding@gmail.com>
Subject: Re: [PATCH] pwm: fi pwm-rz-mtu3.c build errors
Date: Mon, 17 Jul 2023 23:44:40 -0700 [thread overview]
Message-ID: <f0586356-c7f2-c8dd-fbac-ab874dc94f23@gmail.com> (raw)
In-Reply-To: <OS0PR01MB5922C3D065F47297A9620A4A8638A@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On 7/17/23 23:42, Biju Das wrote:
>
>
>> -----Original Message-----
>> From: Randy Dunlap <rd.dunlab@gmail.com>
>> Sent: Tuesday, July 18, 2023 7:38 AM
>> To: linux-kernel@vger.kernel.org; linux-pwm@vger.kernel.org
>> Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>; Thierry Reding
>> <thierry.reding@gmail.com>; Biju Das <biju.das.jz@bp.renesas.com>
>> Subject: Re: [PATCH] pwm: fi pwm-rz-mtu3.c build errors
>>
>> On 7/17/23 22:59, Randy Dunlap wrote:
>>> From: Randy Dunlap <rdunlap@infradead.org>
>>>
>>>
>>> Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver")
>>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>>
>> Oops, I should resend that with corrected email addresses. Sorry.
>
> Also typo in patch header "pwm: fi pwm-rz-mtu3.c build errors" ??
Yes, I saw & fixed that one.
> Not sure fixes tag should be
> b8b28b718ddd ("mfd: Add module build support for RZ/G2L MTU3a")
> or
> 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver")
It's the PWM Kconfig entry that is incorrect AFAICT.
thanks.
--
~Randy
next prev parent reply other threads:[~2023-07-18 6:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 5:59 [PATCH] pwm: fi pwm-rz-mtu3.c build errors Randy Dunlap
2023-07-18 6:37 ` Biju Das
2023-07-18 6:37 ` Randy Dunlap
2023-07-18 6:42 ` Biju Das
2023-07-18 6:44 ` Randy Dunlap [this message]
2023-07-18 6:52 ` Biju Das
2023-07-18 9:00 ` Uwe Kleine-König
2023-07-18 9:22 ` Biju Das
2023-07-18 11:35 ` Biju Das
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=f0586356-c7f2-c8dd-fbac-ab874dc94f23@gmail.com \
--to=rd.dunlab@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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