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]
Date: Fri, 19 Apr 2024 10:05:15 +0000
From: Maarten Brock <Maarten.Brock@...ls.nl>
To: Konstantin Pugin <rilian.la.te@...ru>
CC: Konstantin Pugin <ria.freelander@...il.com>, Greg Kroah-Hartman
	<gregkh@...uxfoundation.org>, Jiri Slaby <jirislaby@...nel.org>, Hugo
 Villeneuve <hvilleneuve@...onoff.com>, Andy Shevchenko
	<andriy.shevchenko@...ux.intel.com>, Lech Perczak
	<lech.perczak@...lingroup.com>, Ilpo Järvinen
	<ilpo.jarvinen@...ux.intel.com>, Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>
Subject: RE: [PATCH v3 0/3] add support for EXAR XR20M1172 UART

> From: Konstantin Pugin <rilian.la.te@...ru>
> Subject: [PATCH v3 0/3] add support for EXAR XR20M1172 UART

What is the policy in the kernel sources for the name of the manufacturer?
This driver never had special support for the EXAR chips when it was still EXAR.
Since 2017 it is now part of MaxLinear. Should the driver use the name of the
original manufacturer or the name of the manufacturer at the time of addition
to the sources?

Kind regards,
Maarten

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ