From: "Arnd Bergmann" <arnd@arndb.de>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Jens Wiklander" <jens.wiklander@linaro.org>,
"Olof Johansson" <olof@lixom.net>
Cc: ARM <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the tee tree
Date: Tue, 05 Mar 2024 07:44:18 +0100 [thread overview]
Message-ID: <154d19f0-1ed8-415c-8c3a-e15b9e7cd4a4@app.fastmail.com> (raw)
In-Reply-To: <20240305100727.004a6dcc@canb.auug.org.au>
On Tue, Mar 5, 2024, at 00:07, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the arm-soc tree as a different commit
> (but the same patch):
>
> 1d044941d538 ("tee: make tee_bus_type const")
Thanks, this was intentional as I ended up cherry-picking the commit
instead of merging. I expect that Jens will drop this branch now.
Arnd
next prev parent reply other threads:[~2024-03-05 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 23:07 linux-next: duplicate patch in the tee tree Stephen Rothwell
2024-03-05 6:44 ` Arnd Bergmann [this message]
2024-03-05 7:30 ` Jens Wiklander
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=154d19f0-1ed8-415c-8c3a-e15b9e7cd4a4@app.fastmail.com \
--to=arnd@arndb.de \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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).