From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Joel Stanley <joel@jms•id.au>, Jeremy Kerr <jk@ozlabs•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 fsi tree
Date: Tue, 15 Aug 2023 21:40:10 +1000 [thread overview]
Message-ID: <20230815214010.712651b9@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
Hi all,
The following commits are also in the char-misc tree as different
commits (but the same patches):
2ecbdc7eea63 ("dt-bindings: fsi: Document the IBM I2C Responder virtual FSI master")
366b119391d1 ("fsi: Add IBM I2C Responder virtual FSI master")
5b4ffc4030fb ("fsi: Add I2C Responder SCOM driver")
83ec2bf4d7d2 ("docs: ABI: fix spelling/grammar in SBEFIFO timeout interface")
c0d1c32d8bcb ("fsi: master-ast-cf: Add MODULE_FIRMWARE macro")
f432b1cf7820 ("fsi: fix some spelling mistakes in comment")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2023-08-15 11:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230815214010.712651b9@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnd@arndb$(echo .)de \
--cc=greg@kroah$(echo .)com \
--cc=jk@ozlabs$(echo .)org \
--cc=joel@jms$(echo .)id.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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