linux-kernel - Re: [PATCH v7 9/9] misc: add FPC202 dual port controller driver

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: <2025022049-shrink-worrisome-2872@gregkh>
Date: Thu, 20 Feb 2025 13:13:04 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
	Romain Gantois <romain.gantois@...tlin.com>,
	Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
	Luca Ceresoli <luca.ceresoli@...tlin.com>,
	Andi Shyti <andi.shyti@...nel.org>, Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Derek Kiernan <derek.kiernan@....com>,
	Dragan Cvetic <dragan.cvetic@....com>,
	Arnd Bergmann <arnd@...db.de>,
	Mauro Carvalho Chehab <mchehab@...nel.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>,
	Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
	Kory Maincent <kory.maincent@...tlin.com>,
	linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org, linux-media@...r.kernel.org,
	linux-gpio@...r.kernel.org
Subject: Re: [PATCH v7 9/9] misc: add FPC202 dual port controller driver

On Thu, Feb 20, 2025 at 01:09:03PM +0100, Wolfram Sang wrote:
> 
> > as this is a i2c_driver, why isn't it in drivers/i2c/ somewhere?  Why
> > misc?
> 
> Because drivers/i2c is only for I2C controllers and this is not a
> controller. Other address translators also reside in their respective
> subsystem, e.g. media for GMSL (de-)serializers. I don't know this chip,
> maybe it has no "respective" subsystem and, thus, misc?

Ok, but that should be explained in the changelog please :)

thanks,

greg k-h