From: Vinod Koul <vkoul@kernel.org>
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 dmaengine tree
Date: Wed, 23 Oct 2024 11:06:26 +0530 [thread overview]
Message-ID: <ZxiLWoL/kkds7PWd@vaman> (raw)
In-Reply-To: <20241023150813.416aafd7@canb.auug.org.au>
Hi Stephen,
On 23-10-24, 15:08, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the devicetree tree as a different commit
> (but the same patch):
>
> 72c65390c61f ("dt-bindings: Fix array property constraints")
>
> This is commit
>
> a6fa1f9e32f5 ("dt-bindings: Fix array property constraints")
>
> in the devicetree tree.
Okay let this go thru dt tree, I have dropped it now
Thanks for letting me know
--
~Vinod
prev parent reply other threads:[~2024-10-23 5:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 4:08 linux-next: duplicate patch in the dmaengine tree Stephen Rothwell
2024-10-23 5:36 ` Vinod Koul [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=ZxiLWoL/kkds7PWd@vaman \
--to=vkoul@kernel.org \
--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