From: Ralph Siemsen <ralph.siemsen@linaro.org>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: u-boot@lists.denx.de, Hai Pham <hai.pham.ud@renesas.com>,
Lukasz Majewski <lukma@denx.de>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Sean Anderson <seanga2@gmail.com>
Subject: Re: [RFC PATCH v3 3/9] clk: renesas: add R906G032 driver
Date: Wed, 22 Feb 2023 14:32:00 -0500 [thread overview]
Message-ID: <20230222193200.GD50215@maple.netwinder.org> (raw)
In-Reply-To: <0e3597e5-d72a-f246-c779-1fd153299ce8@mailbox.org>
On Wed, Feb 22, 2023 at 07:45:45PM +0100, Marek Vasut wrote:
>On 2/22/23 19:32, Ralph Siemsen wrote:
>>On Wed, Feb 22, 2023 at 06:47:44PM +0100, Marek Vasut wrote:
>>>Are those fixes in mainline Linux ?
>>
>>Yes, they are in mainline:
>>2dee50ab9e72 clk: renesas: r9a06g032: Fix UART clkgrp bitsel
>> merged into 6.0, and also backported to earlier LTS branches
>>2a6da4a11f47 clk: renesas: r9a06g032: Fix the RTC hclock description
>> merged into 5.19, seems to be missing from LTS branches
>
>Use Linux 6.2.y as a base then.
Okay, done.
> And please submit the missing patches for LTS branch inclusion too if
>possible, I guess they were missing Fixes: tag ?
Seems it was part of a series which added support for the RTC device:
https://lore.kernel.org/all/20220421090016.79517-3-miquel.raynal@bootlin.com/
Since it is new feature, I guess one could argue that the clock table
fix is not needed in older LTS kernels, since no driver uses that clock.
But most likely it was just overlooked. I'll check with Miquel.
Regards,
Ralph
next prev parent reply other threads:[~2023-02-22 19:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 15:44 [RFC PATCH v3 0/9] Renesas RZ/N1 SoC initial support Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 1/9] ARM: armv7: add non-SPL enable for Cortex SMPEN Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 2/9] clk: renesas: prepare for non-RCAR clock drivers Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 3/9] clk: renesas: add R906G032 driver Ralph Siemsen
2023-02-22 16:06 ` Marek Vasut
2023-02-22 16:57 ` Ralph Siemsen
2023-02-22 17:07 ` Marek Vasut
2023-02-22 17:21 ` Ralph Siemsen
2023-02-22 17:47 ` Marek Vasut
2023-02-22 18:32 ` Ralph Siemsen
2023-02-22 18:45 ` Marek Vasut
2023-02-22 19:32 ` Ralph Siemsen [this message]
2023-02-23 0:12 ` Marek Vasut
2023-02-23 7:17 ` Miquel Raynal
2023-02-23 13:56 ` Marek Vasut
2023-02-23 14:09 ` Miquel Raynal
2023-02-24 15:14 ` Ralph Siemsen
2023-02-24 17:05 ` Marek Vasut
2023-02-24 18:00 ` Ralph Siemsen
2023-02-25 6:16 ` Marek Vasut
2023-02-22 15:44 ` [RFC PATCH v3 4/9] pinctrl: " Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 5/9] ram: cadence: add driver for Cadence EDAC Ralph Siemsen
2023-02-23 19:54 ` Bryan Brattlof
2023-02-24 15:19 ` Ralph Siemsen
2023-03-08 1:19 ` Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 6/9] dts: basic devicetree for Renesas RZ/N1 SoC Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 7/9] ARM: rzn1: basic support " Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 8/9] board: schneider: add RZN1 board support Ralph Siemsen
2023-02-22 15:44 ` [RFC PATCH v3 9/9] tools: spkgimage: add Renesas SPKG format Ralph Siemsen
2023-02-22 19:16 ` Simon Glass
2023-02-22 21:17 ` Ralph Siemsen
2023-02-22 21:20 ` Simon Glass
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=20230222193200.GD50215@maple.netwinder.org \
--to=ralph.siemsen@linaro.org \
--cc=hai.pham.ud@renesas.com \
--cc=lukma@denx.de \
--cc=marek.vasut+renesas@mailbox.org \
--cc=marek.vasut@mailbox.org \
--cc=seanga2@gmail.com \
--cc=u-boot@lists.denx.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 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.