From: Corey Minyard <corey@minyard.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Herring <robh@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the ipmi tree
Date: Wed, 13 Aug 2025 21:41:55 -0500 [thread overview]
Message-ID: <aJ1M883eMiVCtoaO@mail.minyard.net> (raw)
In-Reply-To: <20250814114214.609818aa@canb.auug.org.au>
On Thu, Aug 14, 2025 at 11:42:14AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the devicetree tree as a different commit
> (but the same patch):
I think by normal rules this belongs in my tree. I'm not sure how it
got into the devicetree tree without my ack. Or maybe the rules around
device tree are different.
I'm fine with it either place, though.
-corey
>
> 84e7845761c7 ("dt-bindings: ipmi: aspeed,ast2400-kcs-bmc: Add missing "clocks" property")
>
> This is commit
>
> a2f5472f1cbe ("dt-bindings: ipmi: aspeed,ast2400-kcs-bmc: Add missing "clocks" property")
>
> in the devicetree tree.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2025-08-14 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 1:42 linux-next: duplicate patch in the ipmi tree Stephen Rothwell
2025-08-14 2:41 ` Corey Minyard [this message]
2025-08-14 13:33 ` Rob Herring
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=aJ1M883eMiVCtoaO@mail.minyard.net \
--to=corey@minyard.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robh@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