From: Sinan Kaya <okaya@codeaurora.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-acpi@vger.kernel.org, timur@codeaurora.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Linux PCI <linux-pci@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI/PCI: pci_link: reduce verbosity when IRQ is enabled
Date: Mon, 29 Jan 2018 14:01:59 -0500 [thread overview]
Message-ID: <fde756f4-eb74-4002-6ac4-a44405bad2da@codeaurora.org> (raw)
In-Reply-To: <20180116214939.GC10860@bhelgaas-glaptop.roam.corp.google.com>
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@codeaurora.org>
> Acked-by: Bjorn Helgaas <bhelgaas@google.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?
Sinan
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-01-29 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 18:51 [PATCH] ACPI/PCI: pci_link: reduce verbosity when IRQ is enabled Sinan Kaya
2018-01-16 18:53 ` Sinan Kaya
2018-01-16 21:49 ` Bjorn Helgaas
2018-01-29 19:01 ` Sinan Kaya [this message]
2018-02-01 7:32 ` Rafael J. Wysocki
2018-02-04 9:03 ` Rafael J. Wysocki
2018-02-04 13:43 ` okaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fde756f4-eb74-4002-6ac4-a44405bad2da@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=helgaas@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=timur@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).