From: Valentin Rothberg <valentinrothberg@gmail.com>
To: gregkh@linuxfoundation.org, dledford@redhat.com,
linux-kernel@vger.kernel.org, mike.marciniszyn@intel.com
Cc: Valentin Rothberg <valentinrothberg@gmail.com>
Subject: [PATCH] staging: hfi1: Kconfig: remove 'CONFIG_' prefix
Date: Mon, 17 Aug 2015 13:51:30 +0200 [thread overview]
Message-ID: <1439812290-28059-1-git-send-email-valentinrothberg@gmail.com> (raw)
Remove the 'CONFIG_' prefix of the Kconfig options PRESCAN_RXQ and
SDMA_VERBOSITY in Kconfig. Such prefix in Kconfig requires a double
'CONFIG_CONFIG_' prefix in Make and CPP syntax.
Since both options are referenced in the hfi1 source code as
CONFIG_{PRESCAN_RXQ, SDMA_VERBOSITY} the referencing #ifdef's can now be
compiled.
Signed-off-by: Valentin Rothberg <valentinrothberg@gmail.com>
---
Note that this issue was present since the driver's config files have
been added by commit 8214d07e6f21 ("IB/hfi1: add driver make/config
files"). This change does not introduce any build issues, but I cannot
test it.
I detected this issues with scripts/checkkconfigsymbols.py by diffing
next-20150814..next-20150817
drivers/staging/hfi1/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/hfi1/Kconfig b/drivers/staging/hfi1/Kconfig
index 87a385a02cba..fd25078ee923 100644
--- a/drivers/staging/hfi1/Kconfig
+++ b/drivers/staging/hfi1/Kconfig
@@ -18,14 +18,14 @@ config HFI1_VERBS_31BIT_PSN
---help---
Setting this enables 31 BIT PSN
For verbs RC/UC
-config CONFIG_SDMA_VERBOSITY
+config SDMA_VERBOSITY
bool "Config SDMA Verbosity"
depends on INFINIBAND_HFI1
default n
---help---
This is a configuration flag to enable verbose
SDMA debug
-config CONFIG_PRESCAN_RXQ
+config PRESCAN_RXQ
bool "Enable prescanning of the RX queue for ECNs"
depends on INFINIBAND_HFI1
default n
--
1.9.1
next reply other threads:[~2015-08-17 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 11:51 Valentin Rothberg [this message]
2015-08-17 13:16 ` Marciniszyn, Mike
2015-08-18 19:46 ` Marciniszyn, Mike
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=1439812290-28059-1-git-send-email-valentinrothberg@gmail.com \
--to=valentinrothberg@gmail.com \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.marciniszyn@intel.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
Powered by JetHome