From: Adrian Bunk <bunk@stusta.de>
To: lethal@linux-sh.org, kkojima@rr.iij4u.or.jp
Cc: linuxsh-dev@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [RFC: 2.6 patch] arch/sh/Kconfig: don't source non-existing Kconfig files
Date: Sat, 4 Mar 2006 00:45:48 +0100 [thread overview]
Message-ID: <20060303234548.GG9295@stusta.de> (raw)
arch/sh/Kconfig shouldn't source non-existing Kconfig files.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.16-rc5-sh/arch/sh/Kconfig.old 2006-03-04 00:34:36.000000000 +0100
+++ linux-2.6.16-rc5-sh/arch/sh/Kconfig 2006-03-04 00:44:02.000000000 +0100
@@ -392,9 +392,9 @@
endmenu
-source "arch/sh/boards/renesas/hs7751rvoip/Kconfig"
+#source "arch/sh/boards/renesas/hs7751rvoip/Kconfig"
-source "arch/sh/boards/renesas/rts7751r2d/Kconfig"
+#source "arch/sh/boards/renesas/rts7751r2d/Kconfig"
config SH_PCLK_FREQ
int "Peripheral clock frequency (in Hz)"
next reply other threads:[~2006-03-03 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 23:45 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-08 11:25 [RFC: 2.6 patch] arch/sh/Kconfig: don't source non-existing Kconfig files Adrian Bunk
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=20060303234548.GG9295@stusta.de \
--to=bunk@stusta.de \
--cc=kkojima@rr.iij4u.or.jp \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-dev@lists.sourceforge.net \
/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