public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: linux-i2c@vger.kernel.org, Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH v2 2/2] i2c: i801: Add support for Intel Meteor Lake PCH-S
Date: Wed, 3 May 2023 17:20:19 +0200	[thread overview]
Message-ID: <20230503172019.4c861e1a@endymion.delvare> (raw)
In-Reply-To: <20230424105757.732150-2-jarkko.nikula@linux.intel.com>

Hi Jarkko,

On Mon, 24 Apr 2023 13:57:57 +0300, Jarkko Nikula wrote:
> Add SMBus PCI ID on Intel Meteor Lake PCH-S. Also called as Meteor
> Point-S which is used in the code to distinguish from Meteor Lake-S SoC
> but call both as Meteor Lake in documentation and Kconfig.
> 
> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> ---
> Hi Jean. This is essentially the same than v1 with following minor
> changes:
> v2: "SOC/PCH" -> "SOC and PCH" in documentation and Kconfig. PCI ID
>     define according to updated patch 1/2.

My initial concerns partly stand. You add a device named
"Meteor Point-S" to the driver, but you list that device under name
"Meteor Lake-S" in the documentation (and Kconfig). This is confusing
and I can't see the rationale. Surely the device has one name, and you
should use that name both in the driver and the documentation.

Thanks,
-- 
Jean Delvare
SUSE L3 Support

  parent reply	other threads:[~2023-05-03 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 10:57 [PATCH v2 1/2] i2c: i801: Add support for Intel Meteor Lake-S SoC Jarkko Nikula
2023-04-24 10:57 ` [PATCH v2 2/2] i2c: i801: Add support for Intel Meteor Lake PCH-S Jarkko Nikula
2023-04-25 12:50   ` Andi Shyti
2023-05-03 15:20   ` Jean Delvare [this message]
2023-04-25 12:47 ` [PATCH v2 1/2] i2c: i801: Add support for Intel Meteor Lake-S SoC Andi Shyti
2023-05-03 15:01 ` Jean Delvare

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=20230503172019.4c861e1a@endymion.delvare \
    --to=jdelvare@suse.de \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox