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>, Wolfram Sang <wsa@the-dreams•de>
Cc: 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: Wed, 11 Jun 2025 09:03:08 +1000	[thread overview]
Message-ID: <20250611090308.1e40982e@canb.auug.org.au> (raw)
In-Reply-To: <20250526114315.733b0728@canb.auug.org.au>

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

Hi all,

On Mon, 26 May 2025 11:43:15 +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):
> 
>   a088ce22c118 ("i2c: mlxbf: avoid 64-bit division")
>   50f317545149 ("i2c: viai2c-wmt: Replace dev_err() with dev_err_probe() in probe function")
>   608e2d633096 ("i2c: designware: Don't warn about missing get_clk_rate_khz")
>   481391b537bb ("i2c: designware: Invoke runtime suspend on quick slave re-registration")
>   736f258f0a9b ("i2c-mlxbf: Improve I2C bus timing configuration")
>   a1a8ccd53458 ("i2c-mlxbf: Add repeated start condition support")
>   c43383e2ffa4 ("i2c: xgene-slimpro: Replace dev_err() with dev_err_probe() in probe function")
>   3887d3f64260 ("dt-bindings: i2c: i2c-wmt: Convert to YAML")
>   66234d6c7157 ("i2c: microchip-corei2c: add smbus support")
>   55d144eaea36 ("i2c: mlxbf: Allow build with COMPILE_TEST")
>   52360f31e6ba ("i2c: I2C_DESIGNWARE_AMDISP should depend on DRM_AMD_ISP")
> 
> These are commits
> 
>   2b2805404c92 ("i2c: mlxbf: avoid 64-bit division")
>   3b7d8d151a7e ("i2c: viai2c-wmt: Replace dev_err() with dev_err_probe() in probe function")
>   bdf4442f4c7e ("i2c: designware: Don't warn about missing get_clk_rate_khz")
>   2fe2b969d911 ("i2c: designware: Invoke runtime suspend on quick slave re-registration")
>   e981364d89bf ("i2c-mlxbf: Improve I2C bus timing configuration")
>   6bdc662c05c5 ("i2c-mlxbf: Add repeated start condition support")
>   24d9f6050520 ("i2c: xgene-slimpro: Replace dev_err() with dev_err_probe() in probe function")
>   29b0b4ce6417 ("dt-bindings: i2c: i2c-wmt: Convert to YAML")
>   d6ceb4053826 ("i2c: microchip-corei2c: add smbus support")
>   053859002c20 ("i2c: mlxbf: Allow build with COMPILE_TEST")
>   66e64b457c23 ("i2c: I2C_DESIGNWARE_AMDISP should depend on DRM_AMD_ISP")
> 
> in the i2c tree.

Given that the above commits are the only ones in the i2c-host tree,
can I please have that tree cleaned up.

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2025-06-10 23:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26  1:43 linux-next: duplicate patches in the i2c-host tree Stephen Rothwell
2025-06-10 23:03 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-28  1:59 Stephen Rothwell
2025-04-02  5:19 ` Stephen Rothwell
2024-08-29  0:05 Stephen Rothwell
2024-09-06 21:47 ` Andi Shyti
2024-07-17  1:05 Stephen Rothwell
2024-06-04  1:20 Stephen Rothwell
2024-06-05 22:01 ` 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=20250611090308.1e40982e@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