Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux ACPI <linux-acpi@vger.kernel.org>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: [PATCH v1 0/4] ACPI: PCI: Unify printing of messages
Date: Sat, 20 Feb 2021 17:24:31 +0800	[thread overview]
Message-ID: <7de92ec8-3a15-6165-2384-15d301e7b568@huawei.com> (raw)
In-Reply-To: <4822757.tvZ08WQ2Gl@kreacher>

On 2021/2/20 2:14, Rafael J. Wysocki wrote:
> Hi All,
> 
> This series gets rid of ACPICA debugging from non-ACPICA code related to PCI
> (patches [1-3/4]) and replaces direct printk() usage in pci_link.c with
> pr_*() or acpi_handle_*().
> 
> Please refer to the patch changelogs for details.

Looks good to me,

Reviewed-by: Hanjun Guo <guohanjun@huawei.com>

Thanks
Hanjun

  parent reply	other threads:[~2021-02-20  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 18:14 [PATCH v1 0/4] ACPI: PCI: Unify printing of messages Rafael J. Wysocki
2021-02-19 18:15 ` [PATCH v1 1/4] ACPI: PCI: IRQ: Consolidate printing diagnostic messages Rafael J. Wysocki
2021-02-19 18:16 ` [PATCH v1 2/4] ACPI: PCI: Replace ACPI_DEBUG_PRINT() and ACPI_EXCEPTION() Rafael J. Wysocki
2021-02-19 18:16 ` [PATCH v1 3/4] ACPI: PCI: Drop ACPI_PCI_COMPONENT that is not used any more Rafael J. Wysocki
2021-02-19 18:17 ` [PATCH v1 4/4] ACPI: PCI: Replace direct printk() invocations in pci_link.c Rafael J. Wysocki
2021-02-20  9:24 ` Hanjun Guo [this message]
2021-03-03 18:31   ` [PATCH v1 0/4] ACPI: PCI: Unify printing of messages Rafael J. Wysocki

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=7de92ec8-3a15-6165-2384-15d301e7b568@huawei.com \
    --to=guohanjun@huawei.com \
    --cc=helgaas@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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