From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Will Deacon <will@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the asm-generic tree
Date: Thu, 25 May 2023 09:22:02 +1000 [thread overview]
Message-ID: <20230525092202.78a1fb01@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
b1e7601203a8 ("arm64: vdso: Pass (void *) to virt_to_page()")
This is commit
b0abde80620f ("arm64: vdso: Pass (void *) to virt_to_page()")
in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-05-24 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 23:22 Stephen Rothwell [this message]
2023-05-25 13:41 ` linux-next: duplicate patches in the asm-generic tree Linus Walleij
2023-05-25 16:41 ` Arnd Bergmann
2023-05-29 11:36 ` Linus Walleij
2023-06-01 8:48 ` Arnd Bergmann
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=20230525092202.78a1fb01@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=will@kernel.org \
/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