linux-kernel - Re: [RFC PATCH RESEND] i2c-piix4: Add Hygon Dhyana SMBus support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1556297285.22365.4.camel@suse.de>
Date:   Fri, 26 Apr 2019 18:48:05 +0200
From:   Jean Delvare <jdelvare@...e.de>
To:     Pu Wen <puwen@...on.cn>
Cc:     bp@...en8.de, linux-i2c@...r.kernel.org,
        linux-kernel@...r.kernel.org, stable <stable@...r.kernel.org>
Subject: Re: [RFC PATCH RESEND] i2c-piix4: Add Hygon Dhyana SMBus support

On Fri, 2019-04-26 at 22:23 +0800, Pu Wen wrote:
> On 2019/4/26 17:38, Jean Delvare wrote:
> > I would like you to also document the new supported chipset in
> > drivers/i2c/busses/Kconfig and Documentation/i2c/busses/i2c-piix4 as
> > well as in the header comment of i2c-piix4.c itself. I know it seems
> > redundant but it helps the user know which driver they need.
> 
> Because Hygon uses the same PCI device ID of AMD's, so is it appropriate 
> to document with the name "Hygon CZ" or just "Hygon"?

"Hygon CZ" please, as Hygon is the vendor not the device, and I can
imagine you may create more devices in the future.

Thanks,
-- 
Jean Delvare
SUSE L3 Support