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: Mon, 21 Jul 2025 09:03:43 +1000 [thread overview]
Message-ID: <20250721090343.5cd192eb@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
975b02f641ed ("i2c: stm32f7: unmap DMA mapped buffer")
36ae42978569 ("i2c: stm32: fix the device used for the DMA map")
cfba2fe76b2b ("i2c: omap: Fix an error handling path in omap_i2c_probe()")
7c18e08f4c3a ("i2c: omap: Handle omap_i2c_init() errors in omap_i2c_probe()")
These are commits
6aae87fe7f18 ("i2c: stm32f7: unmap DMA mapped buffer")
c870cbbd71fc ("i2c: stm32: fix the device used for the DMA map")
60c016afccac ("i2c: omap: Fix an error handling path in omap_i2c_probe()")
a9503a2ecd95 ("i2c: omap: Handle omap_i2c_init() errors in omap_i2c_probe()")
in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-07-20 23:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 23:03 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-09 21:12 linux-next: duplicate patches in the i2c-host-fixes tree Stephen Rothwell
2025-12-09 21:23 ` Stephen Rothwell
2025-12-14 22:02 ` Stephen Rothwell
2025-12-16 21:18 ` Stephen Rothwell
2024-03-11 21:15 Stephen Rothwell
2024-03-12 10:42 ` Andi Shyti
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=20250721090343.5cd192eb@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