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] [day] [month] [year] [list]
Message-ID: <20250201155009.GA211663@kernel.org>
Date: Sat, 1 Feb 2025 15:50:09 +0000
From: Simon Horman <horms@...nel.org>
To: Lorenzo Bianconi <lorenzo@...nel.org>
Cc: netdev@...r.kernel.org, andrew+netdev@...n.ch, davem@...emloft.net,
	edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
	nbd@....name, sean.wang@...iatek.com, ansuelsmth@...il.com,
	upstream@...oha.com
Subject: Re: Move airoha in a dedicated folder

On Sat, Feb 01, 2025 at 01:44:53PM +0100, Lorenzo Bianconi wrote:
> Hi all,
> 
> Since more features are on the way for airoha_eth driver (support for flowtable
> hw offloading, 10g phy support, ..), I was wondering if it is neater to move
> the driver in a dedicated folder (e.g. drivers/net/ethernet/airoha or
> drivers/net/ethernet/mediatek/airoha) or if you prefer to keep current
> approach. Thanks.

<2c>

Hi Lorenzo,

There already seem drivers to be drivers under drivers/net/ethernet/mediatek/
which are built from more than once .c file. So I think it is fine
to leave Airoha's source there. But, OTOH, I do think it would
be neater to move it into it's own directory. Which is to say,
I for one am happy either way.

If you do chose to go for a new directory, I would suggest
drivers/net/ethernet/mediatek/airoha assuming as it is a Mediatek device.

</2c>



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ