From: Adrian Bunk <bunk@stusta.de>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/scsi/qla2xxx/Kconfig: two fixes
Date: Sat, 7 Jan 2006 00:09:35 +0100 [thread overview]
Message-ID: <20060106230935.GC3774@stusta.de> (raw)
In-Reply-To: <20060106211241.GG13844@andrew-vasquezs-powerbook-g4-15.local>
On Fri, Jan 06, 2006 at 01:12:41PM -0800, Andrew Vasquez wrote:
> On Fri, 06 Jan 2006, Adrian Bunk wrote:
>
> > This patch contains the following fixes for
> > drivers/scsi/qla2xxx/Kconfig:
> > - add a help text for SCSI_QLA2XXX_EMBEDDED_FIRMWARE
> > - the firmware modules must depend on SCSI_QLA2XXX to prevent
> > illegal configurations like SCSI_QLA2XXX=m, SCSI_QLA21XX=y
> >
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> Ack.
There's another bug that must be fixed:
SCSI_QLA2XXX must be renamed.
The problem is that up to 2.6.15, it was a not user visible variable
that was set for _everyone_ with SCSI && PCI and that didn't have any
influence on what was built.
E.g. it is set in the .config for my computer since my computer has PCI
cards and I'm using USB mass storage.
Due to the change of SCSI_QLA2XXX to a user-visible option that builds
the driver, this means that suddenly after upgrading the kernel and
running "make oldconfig" a SCSI driver gets built the user never
selected.
Do you have any suggestions for a new name?
We could e.g. name it SCSI_QLAXXXX since the driver also supports
6312/6322, or name it simply SCSI_QLA.
> Andrew Vasquez
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-01-06 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 16:34 [2.6 patch] drivers/scsi/qla2xxx/Kconfig: two fixes Adrian Bunk
2006-01-06 21:12 ` Andrew Vasquez
2006-01-06 23:09 ` Adrian Bunk [this message]
2006-01-07 23:50 ` Matthew Wilcox
2006-01-09 17:56 ` Andrew Vasquez
2006-01-09 18:17 ` Andrew Vasquez
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=20060106230935.GC3774@stusta.de \
--to=bunk@stusta.de \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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