From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andi Shyti <andi.shyti@kernel.org>
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 i2c-host-fixes tree
Date: Tue, 12 Mar 2024 08:15:58 +1100 [thread overview]
Message-ID: <20240312081558.014deb45@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
1f78f0901011 ("i2c: aspeed: Fix the dummy irq expected print")
7c16cfd69d51 ("i2c: i801: Avoid potential double call to gpiod_remove_lookup_table")
ace9dc1d1251 ("i2c: wmt: Fix an error handling path in wmt_i2c_probe()")
b60b86b55400 ("i2c: i801: Fix using mux_pdev before it's set")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-03-11 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 21:15 Stephen Rothwell [this message]
2024-03-12 10:42 ` linux-next: duplicate patches in the i2c-host-fixes tree Andi Shyti
-- strict thread matches above, loose matches on Subject: below --
2024-02-18 21:23 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=20240312081558.014deb45@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andi.shyti@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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;
as well as URLs for NNTP newsgroup(s).