linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Punit Agrawal <punit.agrawal@arm.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Alexey Klimov <alexey.klimov@arm.com>,
	linux-kernel@vger.kernel.org, lorenzo.pieralisi@arm.com,
	sudeep.holla@arm.com, Jassi Brar <jassisinghbrar@gmail.com>
Subject: Re: [PATCH 2/4] mailbox: pcc: Drop uninformative output during boot
Date: Tue, 01 Aug 2017 09:57:14 +0100	[thread overview]
Message-ID: <87k22ny8b9.fsf@e105922-lin.cambridge.arm.com> (raw)
In-Reply-To: <d136e72a-c451-e1e8-a9d1-2de6e82f7a99@intel.com> (Rafael J. Wysocki's message of "Tue, 1 Aug 2017 00:23:51 +0200")

"Rafael J. Wysocki" <rafael.j.wysocki@intel.com> writes:

> On 7/31/2017 7:47 PM, Alexey Klimov wrote:
>> (keeping Rafael in c/c per Jassi suggestion)
>>
>> On Thu, Jul 20, 2017 at 12:04 PM, Punit Agrawal <punit.agrawal@arm.com> wrote:
>>> When booting on an ACPI enabled system that does not provide the
>>> Platform Communications Channel Table (PCCT), the pcc mailbox driver
>>> prints -
>>>
>>> [    0.484261] PCCT header not found.
>> Ah. I thought this was already removed ages ago. Thanks for removing this.
>>   
>>> during probe before returning -ENODEV.
>>>
>>> This message clutters the bootlog and doesn't provide any useful
>>> information. Drop this message.
>>>
>>> Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
>>> Cc: Jassi Brar <jassisinghbrar@gmail.com>
>> Acked-by: Alexey Klimov <alexey.klimov@arm.com>
>>
> Please resend this, including all applicable tags, with a CC to
> linux-acpi@vger.kernel.org for easier processing.

Thanks Jassi for adding the appropriate folks on this
patch. get_maintainer.pl threw me off on this one. ;)

I'll add the tags (Thanks, Alexey) and re-send.

>
> Thanks,
>
> Rafael

  reply	other threads:[~2017-08-01  8:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 11:03 [PATCH 0/4] Drop uninformative messages from bootlog Punit Agrawal
2017-07-20 11:03 ` [PATCH 1/4] arm64/numa: Drop duplicate message Punit Agrawal
2017-07-20 11:04 ` [PATCH 2/4] mailbox: pcc: Drop uninformative output during boot Punit Agrawal
     [not found]   ` <874ltt0w7w.fsf@e105922-lin.cambridge.arm.com>
2017-07-31 16:43     ` Jassi Brar
2017-07-31 17:47   ` Alexey Klimov
2017-07-31 22:23     ` Rafael J. Wysocki
2017-08-01  8:57       ` Punit Agrawal [this message]
2017-07-20 11:04 ` [PATCH 3/4] ACPI / APEI: Drop uninformative messages " Punit Agrawal
2017-07-20 11:17   ` Borislav Petkov
2017-07-20 12:29     ` Punit Agrawal
2017-07-20 13:54       ` Borislav Petkov
2017-07-20 17:50         ` Punit Agrawal
2017-07-21 13:27           ` Borislav Petkov
2017-07-27  9:35             ` Punit Agrawal
2017-07-27  9:52               ` Borislav Petkov
2017-07-27  9:55                 ` Punit Agrawal
2017-07-20 11:04 ` [PATCH 4/4] xen: Drop un-informative message " Punit Agrawal
2017-07-20 21:20   ` Boris Ostrovsky
2017-07-21 10:12     ` [Xen-devel] " Punit Agrawal
2017-07-21 10:19       ` Juergen Gross
2017-07-21 10:21         ` Punit Agrawal
2017-07-28  9:34   ` Juergen Gross

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=87k22ny8b9.fsf@e105922-lin.cambridge.arm.com \
    --to=punit.agrawal@arm.com \
    --cc=alexey.klimov@arm.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sudeep.holla@arm.com \
    /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).