From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>
Cc: <linuxarm@huawei.com>, Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [PATCH] PCI: asm-generic/pci_iomap: Correct wrong comment for #endif
Date: Tue, 3 Aug 2021 20:30:14 +0800 [thread overview]
Message-ID: <20210803123014.2963814-1-Jonathan.Cameron@huawei.com> (raw)
If we are going to have comments on header guard #endifs then they should
be correct and match the #ifndef
I'm guessing this one is a cut and paste error or has bit rotted.
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
---
include/asm-generic/pci_iomap.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/asm-generic/pci_iomap.h b/include/asm-generic/pci_iomap.h
index d4f16dcc2ed7..df636c6d8e6c 100644
--- a/include/asm-generic/pci_iomap.h
+++ b/include/asm-generic/pci_iomap.h
@@ -52,4 +52,4 @@ static inline void __iomem *pci_iomap_wc_range(struct pci_dev *dev, int bar,
}
#endif
-#endif /* __ASM_GENERIC_IO_H */
+#endif /* __ASM_GENERIC_PCI_IOMAP_H */
--
2.19.1
next reply other threads:[~2021-08-03 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 12:30 Jonathan Cameron [this message]
2021-08-20 21:17 ` [PATCH] PCI: asm-generic/pci_iomap: Correct wrong comment for #endif 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=20210803123014.2963814-1-Jonathan.Cameron@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.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).