From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: <hch@infradead.org>, <linux-kernel@vger.kernel.org>,
<gregkh@linuxfoundation.org>, <linux-pci@vger.kernel.org>,
<bhelgaas@google.com>
Cc: <stefanha@redhat.com>, <oren@nvidia.com>, <kw@linux.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [PATCH v3 1/2] driver core: use NUMA_NO_NODE during device_initialize
Date: Mon, 4 Oct 2021 16:34:52 +0300 [thread overview]
Message-ID: <20211004133453.18881-1-mgurtovoy@nvidia.com> (raw)
Don't use (-1) constant for setting initial device node. Instead, use
the generic NUMA_NO_NODE definition to indicate that "no node id
specified".
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
---
changes from v2:
- code conventions changes for patch 2/2 (Krzysztof)
- added Reviewed-by signatures for patch 2/2 (Stefan, Krzysztof)
changes from v1:
- added patch 2/2 (Krzysztof)
- added Reviewed-by signature (Stefan)
---
drivers/base/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 15986cc2fe5e..a705b85656df 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -2874,7 +2874,7 @@ void device_initialize(struct device *dev)
spin_lock_init(&dev->devres_lock);
INIT_LIST_HEAD(&dev->devres_head);
device_pm_init(dev);
- set_dev_node(dev, -1);
+ set_dev_node(dev, NUMA_NO_NODE);
#ifdef CONFIG_GENERIC_MSI_IRQ
raw_spin_lock_init(&dev->msi_lock);
INIT_LIST_HEAD(&dev->msi_list);
--
2.18.1
next reply other threads:[~2021-10-04 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 13:34 Max Gurtovoy [this message]
2021-10-04 13:34 ` [PATCH v3 2/2] PCI/sysfs: use NUMA_NO_NODE macro Max Gurtovoy
2021-10-04 19:04 ` Krzysztof Wilczyński
2021-10-08 22:25 ` Bjorn Helgaas
2021-10-10 8:36 ` Max Gurtovoy
2021-10-11 14:06 ` Bjorn Helgaas
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=20211004133453.18881-1-mgurtovoy@nvidia.com \
--to=mgurtovoy@nvidia.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=oren@nvidia.com \
--cc=stefanha@redhat.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).