public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Moritz Fischer <mdf@kernel.org>, Xu Yilun <yilun.xu@intel.com>,
	Wu Hao <hao.wu@intel.com>, 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 fpga-fixes tree
Date: Wed, 31 May 2023 10:19:25 +1000	[thread overview]
Message-ID: <20230531101925.39360756@canb.auug.org.au> (raw)

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

Hi all,

The following commits are also in the char-misc.current tree as different
commits (but the same patches):

  d8bdc50012fe ("dt-bindings: fpga: replace Ivan Bornyakov maintainership")
  feeb9c9219bd ("MAINTAINERS: update Microchip MPF FPGA reviewers")

These are commits

  9da6225bc737 ("dt-bindings: fpga: replace Ivan Bornyakov maintainership")
  929f4e7c06ca ("MAINTAINERS: update Microchip MPF FPGA reviewers")

in the char-misc.current tree.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2023-05-31  0:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31  0:19 Stephen Rothwell [this message]
2023-05-31 15:22 ` linux-next: duplicate patches in the fpga-fixes tree Xu Yilun
  -- strict thread matches above, loose matches on Subject: below --
2023-10-25  0:37 Stephen Rothwell
2023-10-29 20:52 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=20230531101925.39360756@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=greg@kroah.com \
    --cc=hao.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=yilun.xu@intel.com \
    /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