public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
	Jean Delvare <jdelvare@suse.com>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH RFC 2/2] i2c: i801: Call i2c_register_spd for muxed child segments
Date: Mon, 25 Mar 2024 18:36:05 +0100	[thread overview]
Message-ID: <ZgG2BbOSO6GOo8yK@shikoro> (raw)
In-Reply-To: <b4cf0d37-f597-4218-9773-dc6eb8a0dc2a@gmail.com>

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


> Now that 6.9-rc1 is out, we would have several weeks in linux-next
> before 6.10-rc1. Would it be ok for you to apply the patch and see
> whether we get any feedback from linux-next users?

Yes, we can do that.

> If yes, can you apply it as-is, or shall I resubmit the patch?

This is a question for Andi who picks up driver patches meanwhile.


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

  reply	other threads:[~2024-03-25 17:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 22:24 [PATCH RFC 0/2] i2c: i801: Call i2c_register_spd for muxed child segments Heiner Kallweit
2024-02-22 22:24 ` [PATCH RFC 1/2] i2c: smbus: Prepare i2c_register_spd for usage on muxed segments Heiner Kallweit
2024-02-26 10:32   ` Wolfram Sang
2024-03-02 20:21     ` Heiner Kallweit
2024-03-03 12:49       ` Wolfram Sang
2024-02-22 22:25 ` [PATCH RFC 2/2] i2c: i801: Call i2c_register_spd for muxed child segments Heiner Kallweit
2024-02-26 10:36   ` Wolfram Sang
2024-03-02 20:23     ` Heiner Kallweit
2024-03-25 12:34     ` Heiner Kallweit
2024-03-25 17:36       ` Wolfram Sang [this message]
2024-03-26 20:37         ` Heiner Kallweit

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=ZgG2BbOSO6GOo8yK@shikoro \
    --to=wsa@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-i2c@vger.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