From: Hans Zhang <18255117159@163.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: lpieralisi@kernel.org, bhelgaas@google.com,
manivannan.sadhasivam@linaro.org, kw@linux.com,
cassel@kernel.org, robh@kernel.org, jingoohan1@gmail.com,
thomas.richard@bootlin.com, linux-pci@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10 2/6] PCI: Clean up __pci_find_next_cap_ttl() readability
Date: Tue, 29 Apr 2025 23:26:15 +0800 [thread overview]
Message-ID: <4ee5d1cd-bf48-48d4-aa9c-051c5103bc0c@163.com> (raw)
In-Reply-To: <66cdb108-80f5-fe7c-329b-8c60caf55b64@linux.intel.com>
On 2025/4/29 23:17, Ilpo Järvinen wrote:
>> #include <linux/acpi.h>
>> +#include <linux/align.h>
>> #include <linux/kernel.h>
>> #include <linux/delay.h>
>> #include <linux/dmi.h>
>> @@ -30,6 +31,7 @@
>> #include <asm/dma.h>
>> #include <linux/aer.h>
>> #include <linux/bitfield.h>
>> +#include <uapi/linux/pci_regs.h>
>
> linux/pci.h will pull this in through <uapi/linux/pci.h> so you don't need
> to add it (basically anywhere).
Dear Ilpo,
Will delete.
Best regards,
Hans
next prev parent reply other threads:[~2025-04-29 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 12:50 [PATCH v10 0/6] Refactor capability search into common macros Hans Zhang
2025-04-29 12:50 ` [PATCH v10 1/6] PCI: Introduce generic bus config read helper function Hans Zhang
2025-04-29 12:50 ` [PATCH v10 2/6] PCI: Clean up __pci_find_next_cap_ttl() readability Hans Zhang
2025-04-29 15:17 ` Ilpo Järvinen
2025-04-29 15:23 ` Hans Zhang
2025-04-29 15:26 ` Hans Zhang [this message]
2025-04-29 12:50 ` [PATCH v10 3/6] PCI: Refactor capability search into common macros Hans Zhang
2025-04-30 8:03 ` Ilpo Järvinen
2025-04-30 15:49 ` Hans Zhang
2025-04-29 12:50 ` [PATCH v10 4/6] PCI: dwc: Use common PCI host bridge APIs for finding the capabilities Hans Zhang
2025-04-29 12:50 ` [PATCH v10 5/6] PCI: cadence: " Hans Zhang
2025-04-29 12:50 ` [PATCH v10 6/6] PCI: cadence: Use cdns_pcie_find_*capability to avoid hardcode Hans Zhang
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=4ee5d1cd-bf48-48d4-aa9c-051c5103bc0c@163.com \
--to=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=thomas.richard@bootlin.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