linux-kernel - Re: [PATCH v3] USB: serial: ftdi_sio: add support for Altera USB Blaster 3

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: <Z9G8-66NI_5TLSY-@hovoldconsulting.com>
Date: Wed, 12 Mar 2025 17:57:31 +0100
From: Johan Hovold <johan@...nel.org>
To: Boon Khai Ng <boon.khai.ng@...el.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb <linux-usb@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Boon Khai Ng <boon.khai.ng@...era.com>,
	Tien Sung Ang <tien.sung.ang@...era.com>
Subject: Re: [PATCH v3] USB: serial: ftdi_sio: add support for Altera USB
 Blaster 3

On Wed, Mar 12, 2025 at 11:05:44AM +0800, Boon Khai Ng wrote:
> The Altera USB Blaster 3, available as both a cable and an on-board
> solution, is primarily used for programming and debugging FPGAs.

> These configurations allow for flexibility in how the USB Blaster 3 is
> used, depending on the specific needs of the hardware design.
> 
> ---
> 
> v3: Updated PID table.
> 
> PID table in the commit message in v2 missmatched with the PID macro
> defined in the header file, updated the correct table in v3.
> 
> ---
> 
> v2: Update commit message, added PID table, updated the macro name
> 
> Updated the commit message to include more information about the
> background of what is this change about. Added the PID table to
> clarify that the PID associated to the specific hardware configuration
> Updated the macro name in header file from ALTR to ALTERA and also
> the VID's macro name to ALTERA_VID
> 
> Signed-off-by: Boon Khai Ng <boon.khai.ng@...el.com>

Thanks for the update, now applied.

Next time, remember to put your SoB above the (first) cut-off line (---)
so that it is included in the commit message when your patch is applied.
I fixed that up manually this time.

Johan