linux-kernel - Re: [PATCH] serial: 8250_pci: remove unreachable code for ASIX devices

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: <aee8ff85-5716-424e-3773-33700fd90dc2@linux.intel.com>
Date:   Wed, 24 May 2023 19:52:00 +0800
From:   Jiaqing Zhao <jiaqing.zhao@...ux.intel.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] serial: 8250_pci: remove unreachable code for ASIX
 devices



On 2023-05-15 11:49, Greg Kroah-Hartman wrote:
> On Mon, May 15, 2023 at 10:36:30AM +0800, Jiaqing Zhao wrote:
>>
>>
>> On 2023-05-13 18:28, Greg Kroah-Hartman wrote:
>>> On Wed, May 10, 2023 at 02:28:56PM +0000, Jiaqing Zhao wrote:
>>>> PCI_VENDOR_ID_ASIX (0x9710) is the same as PCI_VENDOR_ID_NETMOS. In
>>>> pci_serial_quirks array, the NetMos entry always takes precedence over
>>>> the ASIX entry. So the code for ASIX devices is always unreachable,
>>>> even when it was initially merged. Since the NetMos vendor driver
>>>> doesn't mention such FIFO bug, it's safe to remove the code.
>>>>
>>>> This reverts commit eb26dfe8aa7e ("8250: add support for ASIX devices
>>>> with a FIFO bug").
>>>>
>>>> Signed-off-by: Jiaqing Zhao <jiaqing.zhao@...ux.intel.com>
>>>
>>> Please follow the documented Intel kernel developer requirements before
>>> you submit this again, based on the changes that process will require.
>>>
>>> thanks,
>>>
>>> greg k-h
>>
>> Sorry I am unable to find this "Intel kernel developer requirements". Is
>> there any link or contact where I can find this information? Thank you.
> 
> Contact the Intel Linux developer team and they will point you at them.
> This is a company-wide requirement, it is odd that your normal "Here is
> how you can contribute to Linux!" training at Intel did not cover it?
> 
> thanks,
> 
> greg k-h

I contacted them and there is no reply so far. Could you please tell me if
there is any general available docs about this or point out what I'm doing
wrong in this patch? Thank you very much.