From: Sudeep Holla <sudeep.holla@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the clk tree
Date: Tue, 23 Apr 2024 13:50:11 +0100 [thread overview]
Message-ID: <20240423125011.tjyvkzns7fqpdsl2@bogus> (raw)
In-Reply-To: <20240423103934.399e2a6e@canb.auug.org.au>
On Tue, Apr 23, 2024 at 10:39:34AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in the scmi tree as different commits
> (but the same patches):
>
> 87af9481af53 ("clk: scmi: Add support for get/set duty_cycle operations")
> fa23e091236b ("clk: scmi: Add support for re-parenting restricted clocks")
> c3ad1d0a7ef2 ("clk: scmi: Add support for rate change restricted clocks")
> a1b8faf8784c ("clk: scmi: Add support for state control restricted clocks")
> 2641ee13c449 ("clk: scmi: Allocate CLK operations dynamically")
>
> These are commits
>
> ca82ded0e3dc ("clk: scmi: Add support for get/set duty_cycle operations")
> 3a0501ad6fd4 ("clk: scmi: Add support for re-parenting restricted clocks")
> 4562172e3ec2 ("clk: scmi: Add support for rate change restricted clocks")
> 6785c6c261bd ("clk: scmi: Add support for state control restricted clocks")
> 4196d89b2393 ("clk: scmi: Allocate CLK operations dynamically")
>
> in the scmi tree.
I will drop them from the scmi tree.
--
Regards,
Sudeep
prev parent reply other threads:[~2024-04-23 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 0:39 linux-next: duplicate patches in the clk tree Stephen Rothwell
2024-04-23 12:50 ` Sudeep Holla [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=20240423125011.tjyvkzns7fqpdsl2@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).