From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andi Shyti <andi.shyti@kernel.org>, Wolfram Sang <wsa@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 patch in the i2c-host tree
Date: Wed, 14 Jan 2026 08:03:45 +0100 [thread overview]
Message-ID: <aWc_0VWJPi1cUOTM@ninjato> (raw)
In-Reply-To: <20260114124328.2a986593@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 201 bytes --]
> This is commit
>
> 4fc8450a3495 ("dt-bindings: i2c: atmel,at91sam: add microchip,lan9691-i2c")
>
> in the i2c tree.
Sorry, my fault, I overlooked them in Andi's tree. Dropped it now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-14 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 1:43 linux-next: duplicate patch in the i2c-host tree Stephen Rothwell
2026-01-14 7:03 ` Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-03 1:10 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=aWc_0VWJPi1cUOTM@ninjato \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.