From: Lee Jones <lee@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.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 leds-lj tree
Date: Tue, 31 Jan 2023 09:07:12 +0000 [thread overview]
Message-ID: <Y9jaQNFZGJTMWQxi@google.com> (raw)
In-Reply-To: <20230131144626.13019b79@canb.auug.org.au>
On Tue, 31 Jan 2023, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in other trees as different commits
> (but the same patches):
>
> 0ca222c81977 ("leds: Remove asic3 driver")
> 227e9611cd74 ("dt-bindings: leds: Document Bluetooth and WLAN triggers")
>
> They are commit
>
> fe24d8a40292 ("leds: remove asic3 driver")
>
> from the arm-soc tree, and commit
>
> ef017002b93b ("dt-bindings: leds: Document Bluetooth and WLAN triggers")
>
> from the bluetooth tree.
Luiz, please could you remove these from your tree.
--
Lee Jones [李琼斯]
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.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 leds-lj tree
Date: Tue, 31 Jan 2023 09:07:12 +0000 [thread overview]
Message-ID: <Y9jaQNFZGJTMWQxi@google.com> (raw)
In-Reply-To: <20230131144626.13019b79@canb.auug.org.au>
On Tue, 31 Jan 2023, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in other trees as different commits
> (but the same patches):
>
> 0ca222c81977 ("leds: Remove asic3 driver")
> 227e9611cd74 ("dt-bindings: leds: Document Bluetooth and WLAN triggers")
>
> They are commit
>
> fe24d8a40292 ("leds: remove asic3 driver")
>
> from the arm-soc tree, and commit
>
> ef017002b93b ("dt-bindings: leds: Document Bluetooth and WLAN triggers")
>
> from the bluetooth tree.
Luiz, please could you remove these from your tree.
--
Lee Jones [李琼斯]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-31 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 3:46 linux-next: duplicate patches in the leds-lj tree Stephen Rothwell
2023-01-31 3:46 ` Stephen Rothwell
2023-01-31 9:07 ` Lee Jones [this message]
2023-01-31 9:07 ` Lee Jones
2023-02-01 16:31 ` Arnd Bergmann
2023-02-01 16:31 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2025-01-16 4:24 Stephen Rothwell
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=Y9jaQNFZGJTMWQxi@google.com \
--to=lee@kernel.org \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=olof@lixom.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.