From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel.org>
Cc: 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 bluetooth tree
Date: Mon, 6 May 2024 10:02:27 +1000 [thread overview]
Message-ID: <20240506100227.5931714f@canb.auug.org.au> (raw)
In-Reply-To: <20240503130722.2390748f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
Hi all,
On Fri, 3 May 2024 13:07:22 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> The following commit is also in the mediatek tree as a different commit
> (but the same patch):
>
> f90ac18d01cd ("arm64: dts: mediatek: mt8183-pico6: Fix bluetooth node")
>
> This is commit
>
> 7c9faab9d28f ("arm64: dts: mediatek: mt8183-pico6: Fix bluetooth node")
>
> in the mediatek tree.
The former commit is now commit
cd17bcbd2b33 ("arm64: dts: mediatek: mt8183-pico6: Fix bluetooth node")
in the net tree and commit
a757a088c27b ("arm64: dts: mediatek: mt8183-pico6: Fix bluetooth node")
in the bluetooth tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-05-06 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 3:07 linux-next: duplicate patch in the bluetooth tree Stephen Rothwell
2024-05-06 0:02 ` Stephen Rothwell [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=20240506100227.5931714f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=angelogioacchino.delregno@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.com \
/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).