linux-kernel - Re: [PATCH] ACPI/PCI: pci_link: reduce verbosity when IRQ is enabled

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]

Date:   Sun, 4 Feb 2018 10:03:33 +0100
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Sinan Kaya <okaya@...eaurora.org>
Cc:     Bjorn Helgaas <helgaas@...nel.org>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Timur Tabi <timur@...eaurora.org>,
        linux-arm-msm <linux-arm-msm@...r.kernel.org>,
        linux-arm-kernel@...ts.infradead.org,
        Linux PCI <linux-pci@...r.kernel.org>,
        Len Brown <lenb@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ACPI/PCI: pci_link: reduce verbosity when IRQ is enabled

On Thu, Feb 1, 2018 at 8:32 AM, Rafael J. Wysocki <rafael@...nel.org> wrote:
> On Mon, Jan 29, 2018 at 8:01 PM, Sinan Kaya <okaya@...eaurora.org> wrote:
>> Rafael,
>>
>> On 1/16/2018 4:49 PM, Bjorn Helgaas wrote:
>>> On Tue, Jan 16, 2018 at 01:53:00PM -0500, Sinan Kaya wrote:
>>>> Correcting linux-pci email.
>>>>
>>>> On 1/16/2018 1:51 PM, Sinan Kaya wrote:
>>>>> When ACPI Link object is enabled, the message is printed with a warning
>>>>> prefix. Some test tools are capturing warning and test error types as
>>>>> errors. Let's reduce the verbosity of success case.
>>>>>
>>>>> Signed-off-by: Sinan Kaya <okaya@...eaurora.org>
>>> Acked-by: Bjorn Helgaas <bhelgaas@...gle.com>
>>>
>>> Looks like this was a result of 4d9391557b68 ("ACPI: add missing KERN_*
>>> constants to printks"), which I think added the wrong level in this case.
>>>
>>
>> Any chance of merging this for 4.16?
>
> There is.

This one is already there in the Linus' tree AFAICS.