linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
To: "Krzysztof Wilczyński" <kw@linux.com>
Cc: <bhelgaas@google.com>, <rjw@rjwysocki.net>, <ruscur@russell.cc>,
	<linux-pci@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] PCI: Correct function names in the header
Date: Sat, 27 Mar 2021 16:17:39 +0800	[thread overview]
Message-ID: <df875d72-8acc-defc-5e9d-5b153ce38570@huawei.com> (raw)
In-Reply-To: <YF0zzabwhiKYRq/f@rocinante>

Hi, Krzysztof

On 2021/3/26 9:07, Krzysztof Wilczyński wrote:
> Hi,
> 
> [...]
>>   PCI: acpi_pcihp: Correct acpi_pci_check_ejectable() function name in
>>     the header
>>   PCI/AER: Correct function names in the header
>>   PCI/PME: Correct pcie_pme_init() function name in the header
>>   PCI/ATS: Correct pci_max_pasids() function name in header
> [...]
> 
> All of this has already been fixed in the following series:
> 
>   https://lore.kernel.org/linux-pci/20210311001724.423356-1-kw@linux.com/

Thanks for your remind. I will skip this series in the future.

Thanks,
Xiongfeng

> 
> Krzysztof
> .
> 

      reply	other threads:[~2021-03-27  8:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25  7:51 [PATCH 0/4] PCI: Correct function names in the header Xiongfeng Wang
2021-03-25  7:51 ` [PATCH 1/4] PCI: acpi_pcihp: Correct acpi_pci_check_ejectable() function name " Xiongfeng Wang
2021-03-25 17:31   ` Rafael J. Wysocki
2021-03-25  7:51 ` [PATCH 2/4] PCI/AER: Correct function names " Xiongfeng Wang
2021-03-25 17:30   ` Rafael J. Wysocki
2021-03-26  0:58     ` Xiongfeng Wang
2021-03-25  7:51 ` [PATCH 3/4] PCI/PME: Correct pcie_pme_init() function name " Xiongfeng Wang
2021-03-25  7:51 ` [PATCH 4/4] PCI/ATS: Correct pci_max_pasids() function name in header Xiongfeng Wang
2021-03-26  1:07 ` [PATCH 0/4] PCI: Correct function names in the header Krzysztof Wilczyński
2021-03-27  8:17   ` Xiongfeng Wang [this message]

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=df875d72-8acc-defc-5e9d-5b153ce38570@huawei.com \
    --to=wangxiongfeng2@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=ruscur@russell.cc \
    /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).