Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Palmer Dabbelt <palmerdabbelt@google.com>,
	linux-arch@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH] asm-generic: correct reference to GENERIC_LIB_DEVMEM_IS_ALLOWED
Date: Wed,  6 Oct 2021 16:58:59 +0200	[thread overview]
Message-ID: <20211006145859.9564-1-lukas.bulwahn@gmail.com> (raw)

Commit 527701eda5f1 ("lib: Add a generic version of devmem_is_allowed()")
introduces the config symbol GENERIC_LIB_DEVMEM_IS_ALLOWED, but then
falsely refers to CONFIG_GENERIC_DEVMEM_IS_ALLOWED (note the missing LIB
in the reference) in ./include/asm-generic/io.h.

Luckily, ./scripts/checkkconfigsymbols.py warns on non-existing configs:

GENERIC_DEVMEM_IS_ALLOWED
Referencing files: include/asm-generic/io.h

Correct the name of the config to the intended one.

Fixes: 527701eda5f1 ("lib: Add a generic version of devmem_is_allowed()")
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
 include/asm-generic/io.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/asm-generic/io.h b/include/asm-generic/io.h
index cc7338f9e0d1..6364174504d7 100644
--- a/include/asm-generic/io.h
+++ b/include/asm-generic/io.h
@@ -1125,7 +1125,7 @@ static inline void memcpy_toio(volatile void __iomem *addr, const void *buffer,
 }
 #endif
 
-#ifndef CONFIG_GENERIC_DEVMEM_IS_ALLOWED
+#ifndef CONFIG_GENERIC_LIB_DEVMEM_IS_ALLOWED
 extern int devmem_is_allowed(unsigned long pfn);
 #endif
 
-- 
2.26.2


             reply	other threads:[~2021-10-06 14:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 14:58 Lukas Bulwahn [this message]
2021-10-06 15:17 ` [PATCH] asm-generic: correct reference to GENERIC_LIB_DEVMEM_IS_ALLOWED Arnd Bergmann
2021-10-06 16:52   ` Palmer Dabbelt
2022-07-07 11:40     ` Lukas Bulwahn
2022-07-07 12:13       ` Arnd Bergmann
2022-07-07 12:20         ` Conor.Dooley
2022-07-07 13:07           ` Arnd Bergmann
2022-07-07 14:41             ` Lukas Bulwahn
2022-07-20 10:50               ` Arnd Bergmann
2022-07-21  6:52                 ` Lukas Bulwahn
2022-07-21 20:41                   ` Lukas Bulwahn

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=20211006145859.9564-1-lukas.bulwahn@gmail.com \
    --to=lukas.bulwahn@gmail.com \
    --cc=arnd@arndb.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=palmerdabbelt@google.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