public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andi Shyti <andi.shyti@kernel•org>
Cc: Wolfram Sang <wsa@the-dreams•de>,
	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-host tree
Date: Thu, 6 Jun 2024 08:01:07 +1000	[thread overview]
Message-ID: <20240606080107.1347097a@canb.auug.org.au> (raw)
In-Reply-To: <20240604112010.4b29ffe7@canb.auug.org.au>

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

Hi all,

On Tue, 4 Jun 2024 11:20:10 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> The following commits are also in the i2c tree as different commits
> (but the same patches):
> 
>   5fb9780aa910 ("i2c: Remove I2C_CLASS_SPD")
>   fe69f7d19df7 ("i2c: synquacer: Remove a clk reference from struct synquacer_i2c")
> 
> These are commits
> 
>   e61bcf42d290 ("i2c: Remove I2C_CLASS_SPD")
>   e6722ea6b9ed ("i2c: synquacer: Remove a clk reference from struct synquacer_i2c")
> 
> in the i2c tree.

These latter commits are now in Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-06-05 22:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  1:20 linux-next: duplicate patches in the i2c-host tree Stephen Rothwell
2024-06-05 22:01 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-17  1:05 Stephen Rothwell
2024-08-29  0:05 Stephen Rothwell
2024-09-06 21:47 ` Andi Shyti
2025-03-28  1:59 Stephen Rothwell
2025-04-02  5:19 ` Stephen Rothwell
2025-05-26  1:43 Stephen Rothwell
2025-06-10 23:03 ` 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=20240606080107.1347097a@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=andi.shyti@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=wsa@the-dreams$(echo .)de \
    /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