From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Srini Kandagatla <srinivas.kandagatla@linaro•org>,
Greg KH <greg@kroah•com>, Arnd Bergmann <arnd@arndb•de>
Cc: 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 fastrpc tree
Date: Tue, 30 May 2023 14:37:13 +1000 [thread overview]
Message-ID: <20230530143713.4cd58e31@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
Hi all,
The following commits are also in the char-misc.current tree as different
commits (but the same patches):
3a1f192ad1b4 ("misc: fastrpc: reject new invocations during device removal")
578b3c7d15e6 ("misc: fastrpc: return -EPIPE to invocations on device removal")
5fad4a6b2d8f ("misc: fastrpc: Reassign memory ownership only for remote heap")
dc37d43b894e ("misc: fastrpc: Pass proper scm arguments for secure map request")
These are commits
46248400d81e ("misc: fastrpc: reject new invocations during device removal")
b6a062853ddf ("misc: fastrpc: return -EPIPE to invocations on device removal")
3c7d0079a183 ("misc: fastrpc: Reassign memory ownership only for remote heap")
a6e766dea0a2 ("misc: fastrpc: Pass proper scm arguments for secure map request")
in the char-misc.current tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-05-30 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 4:37 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-04 21:54 linux-next: duplicate patches in the fastrpc tree Stephen Rothwell
2023-10-17 4:00 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=20230530143713.4cd58e31@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnd@arndb$(echo .)de \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=srinivas.kandagatla@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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