public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Wolfram Sang <wsa@the-dreams•de>, 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 tree
Date: Tue, 15 Aug 2023 12:16:43 +1000	[thread overview]
Message-ID: <20230815121643.047c564f@canb.auug.org.au> (raw)

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

Hi all,

The following commits are also in the i2c-host-fixes tree as different
commits (but the same patches):

  27ec43c77b5d ("i2c: tegra: Fix i2c-tegra DMA config option processing")
  3253f6923a78 ("i2c: tiny-usb: check usb base class before assuming the interface on device is for this driver")
  49d4db3953cb ("i2c: designware: Correct length byte validation logic")
  69f035c480d7 ("i2c: designware: Handle invalid SMBus block data response length value")
  b610c4bbd153 ("i2c: imx-lpi2c: return -EINVAL when i2c peripheral clk doesn't work")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2023-08-15  2:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15  2:16 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-07 21:24 linux-next: duplicate patches in the i2c tree Stephen Rothwell
2024-01-07 21:55 ` Wolfram Sang
2024-01-21  9:05 Stephen Rothwell
2024-01-21 12:27 ` Wolfram Sang
2025-07-15  3:06 Stephen Rothwell
2025-07-15  8:01 ` Wolfram Sang

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=20230815121643.047c564f@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