public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Srini Kandagatla <srinivas.kandagatla@linaro•org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation•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 fastrpc tree
Date: Tue, 5 Sep 2023 07:54:17 +1000	[thread overview]
Message-ID: <20230905075417.6de58e76@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 651 bytes --]

Hi all,

The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):

  64227235abd9 ("misc: fastrpc: Pass proper scm arguments for static process init")
  3042d44f7e49 ("misc: fastrpc: Fix incorrect DMA mapping unmap request")
  098316374fea ("misc: fastrpc: Fix remote heap allocation request")

These are commits

  fe6518d547fc ("misc: fastrpc: Pass proper scm arguments for static process init")
  a2cb9cd6a394 ("misc: fastrpc: Fix incorrect DMA mapping unmap request")
  ada6c2d99aed ("misc: fastrpc: Fix remote heap allocation request")

in Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-09-04 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 21:54 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-17  4:00 linux-next: duplicate patches in the fastrpc tree Stephen Rothwell
2023-05-30  4:37 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=20230905075417.6de58e76@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --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