From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Stephen Boyd <sboyd@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
SoC Team <soc@kernel.org>, <linux-clk@vger.kernel.org>,
<mturquette@baylibre.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Conor Dooley <conor@kernel.org>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
<oe-kbuild-all@lists.linux.dev>, <llvm@lists.linux.dev>,
kbuild test robot <lkp@intel.com>
Subject: Re: [GIT PULL] ARM: microchip: clk for 6.18 #1
Date: Wed, 17 Sep 2025 20:23:35 +0200 [thread overview]
Message-ID: <1a740af5-78c9-421f-a58a-fd4a2066493a@microchip.com> (raw)
In-Reply-To: <175808457715.4354.11044142356915096975@lazor>
Stephen,
On 17/09/2025 at 06:49, Stephen Boyd wrote:
> Quoting Nicolas Ferre (2025-09-16 06:19:11)
>> On 16/09/2025 at 10:05, nicolas.ferre@microchip.com wrote:
>>> From: Nicolas Ferre <nicolas.ferre@microchip.com>
>>>
>>> Dear clock maintainers,
>>>
>>> Here are the first clk changes for 6.18.
>>> I don't think they have conflict with changes for the deprecated round_rate()
>>> to determine_rate() topic.
>>> They are in linux-next for a couple of days.
>>
>> But... this series depends on this patch:
>> https://lore.kernel.org/r/20250827145427.46819-4-nicolas.ferre@microchip.com
>>
>> Which will be part of a pull-request to-be-sent soon to arm-soc (which
>> is part of linux-next, so the build error doesn't appear there).
>>
>> Once the pull-request is done, do you prefer that I do an immutable
>> branch between CLK and ARM, that I queue this at91 PM patch into the clk
>> pull-request or that everything goes through arm-soc?
>
> Whatever is required to build the code should be included in the PR. If
> the same commit goes into arm-soc tree that's OK, just make sure the
> branches aren't broken if you checkout a commit anywhere along the
> branch that is sent to clk or arm-soc trees. Broken includes
> functionally broken.
Thanks for your quick response Stephen. v2 of the pull-request has just
been sent.
Best regards,
Nicolas
next prev parent reply other threads:[~2025-09-17 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 8:05 [GIT PULL] ARM: microchip: clk for 6.18 #1 nicolas.ferre
2025-09-16 13:19 ` Nicolas Ferre
2025-09-17 4:49 ` Stephen Boyd
2025-09-17 18:23 ` Nicolas Ferre [this message]
2025-09-17 18:21 ` [GIT PULL v2] " nicolas.ferre
2025-09-21 17:02 ` Stephen Boyd
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=1a740af5-78c9-421f-a58a-fd4a2066493a@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mturquette@baylibre.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sboyd@kernel.org \
--cc=soc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox