linux-kernel - Re: [PATCH v5 3/5] serial: fsl_linflexuart: Be consistent with the name

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: <VI1PR0402MB2863C5C76A9F709B98C7BDE7DF9E0@VI1PR0402MB2863.eurprd04.prod.outlook.com>
Date:   Fri, 4 Oct 2019 13:40:48 +0000
From:   Stefan-gabriel Mirea <stefan-gabriel.mirea@....com>
To:     "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC:     "corbet@....net" <corbet@....net>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "mark.rutland@....com" <mark.rutland@....com>,
        "catalin.marinas@....com" <catalin.marinas@....com>,
        "will@...nel.org" <will@...nel.org>,
        "jslaby@...e.com" <jslaby@...e.com>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v5 3/5] serial: fsl_linflexuart: Be consistent with the
 name

Hello Greg,

On 10/4/2019 4:07 PM, gregkh@...uxfoundation.org wrote:
> On Wed, Oct 02, 2019 at 01:04:42PM +0000, Stefan-gabriel Mirea wrote:
>> --- a/include/uapi/linux/serial_core.h
>> +++ b/include/uapi/linux/serial_core.h
>> @@ -290,7 +290,7 @@
>>  /* Sunix UART */
>>  #define PORT_SUNIX   121
>>
>> -/* Freescale Linflex UART */
>> -#define PORT_LINFLEXUART     121
>> +/* Freescale LINFlexD UART */
>> +#define PORT_LINFLEXUART     122
> 
> This is a different change, and one that should be split out and
> submitted now, for 5.4.  Please do that as the id number is incorrect,
> don't bury a valid change in the middle of a "marketing renamed the
> device" patch :)

I will do that, thanks!

Regards,
Stefan