From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>,
Rob Herring <robh@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
<jic23@kernel.org>
Subject: Re: linux-next: duplicate patch in the iio tree
Date: Wed, 11 Oct 2023 09:15:48 +0100 [thread overview]
Message-ID: <20231011091548.0000396b@Huawei.com> (raw)
In-Reply-To: <20231011081114.2f4d36e4@canb.auug.org.au>
On Wed, 11 Oct 2023 08:11:14 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> 25a0741b55b1 ("dt-bindings: trivial-devices: Fix MEMSIC MXC4005 compatible string")
>
> This is commit
>
> 19007c629c63 ("dt-bindings: trivial-devices: Fix MEMSIC MXC4005 compatible string")
>
> in Linus' tree.
>
That's near the top of my tree so fixing it shouldn't make too much of a mess.
I'll drop it when I'm next on the right machine.
Thanks,
Jonathan
prev parent reply other threads:[~2023-10-11 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 21:11 linux-next: duplicate patch in the iio tree Stephen Rothwell
2023-10-11 8:15 ` Jonathan Cameron [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=20231011091548.0000396b@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--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;
as well as URLs for NNTP newsgroup(s).