linux-kernel - Re: [PATCH 0/5] Parse the PCIE AER structure and set to relevant registers

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:   Tue, 1 Nov 2022 15:25:17 +0800
From:   LeoLiuoc <LeoLiu-oc@...oxin.com>
To:     Bjorn Helgaas <helgaas@...nel.org>
CC:     Sathyanarayanan Kuppuswamy 
        <sathyanarayanan.kuppuswamy@...ux.intel.com>, <rafael@...nel.org>,
        <lenb@...nel.org>, <james.morse@....com>, <tony.luck@...el.com>,
        <bp@...en8.de>, <robert.moore@...el.com>, <ying.huang@...el.com>,
        <rdunlap@...radead.org>, <bhelgaas@...gle.com>,
        <linux-acpi@...r.kernel.org>, <linux-pci@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <devel@...ica.org>,
        <CobeChen@...oxin.com>, <TonyWWang@...oxin.com>,
        <ErosZhang@...oxin.com>
Subject: Re: [PATCH 0/5] Parse the PCIE AER structure and set to relevant
 registers



在 2022/10/28 23:15, Bjorn Helgaas 写道:
> On Fri, Oct 28, 2022 at 07:19:25PM +0800, LeoLiuoc wrote:
>> 在 2022/10/27 12:17, Sathyanarayanan Kuppuswamy 写道:
>>> On 10/26/22 8:14 PM, LeoLiu-oc wrote:
> 
>>> Can you add spec reference?
>>>
>> Please refer to Section 18.3.2 ACPI Error Source of acpi spec v6.3. Links to
>> the online versions of ACPI Spec 6.3 is
>> https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/18_ACPI_Platform_Error_Interfaces/error-source-discovery.html#acpi-error-source.
>>
>> Section 18.3.2.4 describes PCI Express Root Port AER Structure, section
>> 18.3.2.5 describes PCI Express Device AER Structure, section 18.3.2.6
>> describes PCI Express/PCI-X Bridge AER Structure.
> 
> Thanks.  It's OK to have the spec references in the email thread, but
> the real point is that they should be in the commit log and, when it
> makes sense, in code comments.
> 
> Cite the most recent spec version when you can.  In this case, I think
> it is ACPI r6.5.
> 
> Personally I don't really care for URL references because they tend to
> get stale over time as websites are reorganized and domains change.
> Something like "ACPI r6.5, sec 18.3.2.4" is unambiguous and will
> remain usable forever.
> 
> Bjorn

Got it. Thanks for your advice. This will be modified in the next version.

Thanks
leoliu-oc