linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wolfram Sang <wsa@kernel.org>, Andi Shyti <andi.shyti@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the i2c tree
Date: Tue, 15 Jul 2025 10:01:57 +0200	[thread overview]
Message-ID: <aHYK9RWJ7GqTzvY2@shikoro> (raw)
In-Reply-To: <20250715130652.5570887f@canb.auug.org.au>

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


>   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()")

Andi, please do not rebase your host-fixes tree when I already pulled it
but couldn't send it to Linus that week. Please only add to this branch
but do not rebase.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-07-15  8:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15  3:06 linux-next: duplicate patches in the i2c tree Stephen Rothwell
2025-07-15  8:01 ` Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-21  9:05 Stephen Rothwell
2024-01-21 12:27 ` Wolfram Sang
2024-01-07 21:24 Stephen Rothwell
2024-01-07 21:55 ` Wolfram Sang
2023-08-15  2:16 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=aHYK9RWJ7GqTzvY2@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=andi.shyti@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=wsa@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).