From: Rusty Trivial Russell <rusty@rustcorp.com.au>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: geert@linux-m68k.org, linux-scsi@vger.kernel.org
Subject: [TRIVIAL] PATCH 2.5: kconfig sychronise banners (2_16)
Date: Wed, 07 Aug 2002 14:06:07 +1000 [thread overview]
Message-ID: <20020807043056.428DF4B4C@lists.samba.org> (raw)
From: Greg Banks <gnb@alphalink.com.au>
(Included in 2.5)
G'day,
2/5 definitions of CONFIG_BLK_DEV_SR have trivially different banners.
--- trivial-2.4.20-pre1/arch/m68k/config.in.orig 2002-08-07 10:57:32.000000000 +1000
+++ trivial-2.4.20-pre1/arch/m68k/config.in 2002-08-07 10:57:32.000000000 +1000
@@ -205,7 +205,7 @@
if [ "$CONFIG_CHR_DEV_ST" != "n" ]; then
int 'Maximum number of SCSI tapes that can be loaded as modules' CONFIG_ST_EXTRA_DEVS 2
fi
- dep_tristate ' SCSI CD-ROM support' CONFIG_BLK_DEV_SR $CONFIG_SCSI
+ dep_tristate ' SCSI CDROM support' CONFIG_BLK_DEV_SR $CONFIG_SCSI
if [ "$CONFIG_BLK_DEV_SR" != "n" ]; then
bool ' Enable vendor-specific extensions (for SCSI CDROM)' CONFIG_BLK_DEV_SR_VENDOR
int 'Maximum number of CDROM devices that can be loaded as modules' CONFIG_SR_EXTRA_DEVS 2
--- trivial-2.4.20-pre1/drivers/scsi/Config.in.orig 2002-08-07 10:57:32.000000000 +1000
+++ trivial-2.4.20-pre1/drivers/scsi/Config.in 2002-08-07 10:57:32.000000000 +1000
@@ -10,7 +10,7 @@
dep_tristate ' SCSI OnStream SC-x0 tape support' CONFIG_CHR_DEV_OSST $CONFIG_SCSI
-dep_tristate ' SCSI CD-ROM support' CONFIG_BLK_DEV_SR $CONFIG_SCSI
+dep_tristate ' SCSI CDROM support' CONFIG_BLK_DEV_SR $CONFIG_SCSI
if [ "$CONFIG_BLK_DEV_SR" != "n" ]; then
bool ' Enable vendor-specific extensions (for SCSI CDROM)' CONFIG_BLK_DEV_SR_VENDOR
--
Don't blame me: the Monkey is driving
next reply other threads:[~2002-08-07 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 4:06 Rusty Trivial Russell [this message]
2002-08-07 11:35 ` [TRIVIAL] PATCH 2.5: kconfig sychronise banners (2_16) Alan Cox
2002-08-08 2:10 ` Rusty Russell
2002-08-09 13:29 ` Greg Banks
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=20020807043056.428DF4B4C@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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