From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: "ISS StorageDev" <iss_storagedev@hp.com>,
linux-kernel@vger.kernel.org, "Andrew Morton" <akpm@osdl.org>
Subject: Re: [PATCH 7/7] CCISS: run through Lindent
Date: Thu, 15 Jun 2006 09:42:37 -0600 [thread overview]
Message-ID: <200606150942.37627.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF10C524A07@cceexc23.americas.cpqcorp.net>
On Thursday 15 June 2006 08:49, Miller, Mike (OS Dev) wrote
> > -----Original Message-----
> > From: Helgaas, Bjorn
> > Sent: Wednesday, June 14, 2006 6:14 PM
> > To: Miller, Mike (OS Dev)
> > Cc: ISS StorageDev; linux-kernel@vger.kernel.org; Andrew Morton
> > Subject: [PATCH 7/7] CCISS: run through Lindent
> >
> > cciss is full of inconsistent style ("for (" vs. "for(", lines that
> > end with whitespace, lines beginning with a mix of spaces &
> > tabs, etc).
> >
> > This patch changes only whitespace.
> >
> > Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
>
> I agree that we had lots of whitespace garbage and inconsistent styles
> in the driver but I'm not sure I like all the indentation being removed
> from the product table. It makes it a bit harder to read, IMO.
If you are OK with the patch other than the product table, how about
if you apply the patch as-is, and I post a follow-on patch to fix the
indentation?
I'm contemplating more than just a white-space change, and it'd
probably be better to keep the "indent" patch to be white-space
changes only.
The cciss_pci_device_id[] table lists a bunch of subvendor and
subdevice IDs. Is there any reason to check those sub-IDs
explicitly? In other words, we currently list:
{PCI_VENDOR_ID_COMPAQ, PCI_DEVICE_ID_COMPAQ_CISS,
0x0E11, 0x4070, 0, 0, 0},
Could we replace that with:
{PCI_VENDOR_ID_COMPAQ, PCI_DEVICE_ID_COMPAQ_CISS,
PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
This would potentially make the driver claim additional devices.
But do COMPAQ/CISS devices with sub-IDs other than the listed ones
really exist anyway?
Bjorn
next parent reply other threads:[~2006-06-15 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D4CFB69C345C394284E4B78B876C1CF10C524A07@cceexc23.americas.cpqcorp.net>
2006-06-15 15:42 ` Bjorn Helgaas [this message]
2006-06-15 16:01 ` Cameron, Steve
2006-06-15 16:28 ` Miller, Mike (OS Dev)
2006-06-14 23:07 [PATCH 0/7] CCISS cleanups Bjorn Helgaas
[not found] ` <200606141713.46497.bjorn.helgaas@hp.com>
2006-06-15 4:08 ` [PATCH 7/7] CCISS: run through Lindent Bjorn Helgaas
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=200606150942.37627.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=Mike.Miller@hp.com \
--cc=akpm@osdl.org \
--cc=iss_storagedev@hp.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®