linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Wolfram Sang <wsa@kernel.org>, Jean Delvare <jdelvare@suse.de>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: i801: Add support for Intel Alder Lake PCH-P
Date: Mon, 1 Feb 2021 16:02:48 +0200	[thread overview]
Message-ID: <70c0c886-f8bb-1179-3bb9-f805ac7f4800@linux.intel.com> (raw)
In-Reply-To: <20210128085943.GD963@ninjato>

On 1/28/21 10:59 AM, Wolfram Sang wrote:
> On Thu, Jan 14, 2021 at 04:38:11PM +0200, Jarkko Nikula wrote:
>> Add PCI ID of SMBus controller on Intel Alder Lake PCH-P.
>>
>> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> 
> Do we still update Documentation/i2c/busses/i2c-i801.rst?
> 
Actually need to avoid patching it and Kconfig for each new chipset 
variant and make them shorter was my motivation behind commit 
80d943ab19e9 ("i2c: i801: Consolidate chipset names in documentation and 
Kconfig").

Here Alder Lake name was added by the commit 332fdaebb64e ("i2c: i801: 
Add support for Intel Alder Lake PCH-S").

> And maybe we should add Jarkko as i801 maintainer because Jean is usually
> fine with such changes?
> 
I'm not sure am I up to the task? Meaning I don't feel I know it so 
well. I've been mostly adding new PCI IDs to new platforms.

Jarkko

  reply	other threads:[~2021-02-01 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 14:38 [PATCH] i2c: i801: Add support for Intel Alder Lake PCH-P Jarkko Nikula
2021-01-28  8:59 ` Wolfram Sang
2021-02-01 14:02   ` Jarkko Nikula [this message]
2021-02-09 10:45     ` Wolfram Sang
2021-02-26 16:35       ` 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=70c0c886-f8bb-1179-3bb9-f805ac7f4800@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=jdelvare@suse.de \
    --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;
as well as URLs for NNTP newsgroup(s).