From: hechushiguitu666@gmail.com
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"haoyu.lu" <hechushiguitu666@gmail.com>
Subject: [PATCH] PCI: probe: Fix spacing around operators
Date: Tue, 3 Mar 2026 15:36:54 +0800 [thread overview]
Message-ID: <20260303073655.2047-1-hechushiguitu666@gmail.com> (raw)
From: "haoyu.lu" <hechushiguitu666@gmail.com>
Fix checkpatch.pl warnings for missing spaces around operators:
- size-1 -> size - 1
- PCI_BRIDGE_RESOURCES+i -> PCI_BRIDGE_RESOURCES + i
- 60*1000 -> 60 * 1000
Signed-off-by: haoyu.lu <hechushiguitu666@gmail.com>
---
drivers/pci/probe.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
index bccc7a4bdd79..e54fa8a9f377 100644
--- a/drivers/pci/probe.c
+++ b/drivers/pci/probe.c
@@ -119,7 +119,7 @@ static u64 pci_size(u64 base, u64 maxbase, u64 mask)
* Get the lowest of them to find the decode size, and from that
* the extent.
*/
- size = size & ~(size-1);
+ size = size & ~(size - 1);
/*
* base == maxbase can be valid only if the BAR has already been
@@ -594,7 +594,7 @@ void pci_read_bridge_bases(struct pci_bus *child)
pci_bus_remove_resources(child);
for (i = 0; i < PCI_BRIDGE_RESOURCE_NUM; i++)
- child->resource[i] = &dev->resource[PCI_BRIDGE_RESOURCES+i];
+ child->resource[i] = &dev->resource[PCI_BRIDGE_RESOURCES + i];
pci_read_bridge_io(child->self,
child->resource[PCI_BUS_BRIDGE_IO_WINDOW], false);
@@ -2600,7 +2600,7 @@ static struct pci_dev *pci_scan_device(struct pci_bus *bus, int devfn)
struct pci_dev *dev;
u32 l;
- if (!pci_bus_read_dev_vendor_id(bus, devfn, &l, 60*1000))
+ if (!pci_bus_read_dev_vendor_id(bus, devfn, &l, 60 * 1000))
return NULL;
dev = pci_alloc_dev(bus);
--
2.53.0.windows.1
next reply other threads:[~2026-03-03 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 7:36 hechushiguitu666 [this message]
2026-03-03 12:55 ` Ilpo Järvinen
2026-03-04 6:26 ` [PATCH v2] PCI: probe: Use helper macros and constants hechushiguitu666
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=20260303073655.2047-1-hechushiguitu666@gmail.com \
--to=hechushiguitu666@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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
all inboxes | Powered by JetHome®