From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Ingo Korb <ml@akana.de>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/1] ide: ide-generic, add another device exception
Date: Mon, 04 Jun 2007 17:14:56 +0400 [thread overview]
Message-ID: <46641050.1030901@ru.mvista.com> (raw)
In-Reply-To: <46640C30.9050808@gmail.com>
Hello.
Jiri Slaby wrote:
>>>diff --git a/drivers/ide/pci/generic.c b/drivers/ide/pci/generic.c
>>>index f2c5a14..0d51a11 100644
>>>--- a/drivers/ide/pci/generic.c
>>>+++ b/drivers/ide/pci/generic.c
>>>@@ -198,32 +198,41 @@ static ide_pci_device_t generic_chipsets[]
>>>__devinitdata = {
>>> static int __devinit generic_init_one(struct pci_dev *dev, const
>>>struct pci_device_id *id)
>>> {
>>> ide_pci_device_t *d = &generic_chipsets[id->driver_data];
>>>- u16 command;
>>> int ret = -ENODEV;
>>>
>>> /* Don't use the generic entry unless instructed to do so */
>>> if (id->driver_data == 0 && ide_generic_all == 0)
>>> goto out;
>>>
>>>- if (dev->vendor == PCI_VENDOR_ID_UMC &&
>>>- dev->device == PCI_DEVICE_ID_UMC_UM8886A &&
>>>- (!(PCI_FUNC(dev->devfn) & 1)))
>>>- goto out; /* UM8886A/BF pair */
>>>-
>>>- if (dev->vendor == PCI_VENDOR_ID_OPTI &&
>>>- dev->device == PCI_DEVICE_ID_OPTI_82C558 &&
>>>- (!(PCI_FUNC(dev->devfn) & 1)))
>>>- goto out;
>>>-
>>>- if (dev->vendor == PCI_VENDOR_ID_JMICRON) {
>>>- if (dev->device != PCI_DEVICE_ID_JMICRON_JMB368 &&
>>>PCI_FUNC(dev->devfn) != 1)
>>>+ switch (dev->vendor) {
>>>+ case PCI_VENDOR_ID_UMC:
>>>+ if (dev->device == PCI_DEVICE_ID_UMC_UM8886A &&
>>>+ !(PCI_FUNC(dev->devfn) & 1))
>>>+ goto out; /* UM8886A/BF pair */
>>>+ break;
>>>+ case PCI_VENDOR_ID_OPTI:
>>>+ if (dev->device == PCI_DEVICE_ID_OPTI_82C558 &&
>>>+ !(PCI_FUNC(dev->devfn) & 1))
>>>+ goto out;
>>>+ break;
>>>+ case PCI_VENDOR_ID_JMICRON:
>>>+ if (dev->device != PCI_DEVICE_ID_JMICRON_JMB368 &&
>>>+ PCI_FUNC(dev->devfn) != 1)
>>>+ goto out;
>>>+ break;
>>>+ case PCI_VENDOR_ID_NS:
>>>+ if (dev->device == PCI_DEVICE_ID_NS_87410 &&
>>>+ (dev->class >> 8) != PCI_CLASS_STORAGE_IDE)
>>> goto out;
>>>+ break;
>>> }
>> Could you intend the if() conditions carried to another line the way
>>they were intended before?
> I could, if you tell me the reason.
Sorry -- I thought it was a part of kernel style, but it appeared to be my
aesthetical preference only. :-)
> regards,
MBR, Sergei
next prev parent reply other threads:[~2007-06-04 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 9:20 [PATCH 1/1] ide: ide-generic, add another device exception Jiri Slaby
2007-06-04 12:51 ` Sergei Shtylyov
2007-06-04 12:57 ` Jiri Slaby
2007-06-04 13:14 ` Sergei Shtylyov [this message]
2007-06-04 13:16 ` Jiri Slaby
2007-06-08 12:18 ` Bartlomiej Zolnierkiewicz
2007-06-08 13:59 ` Jeff Garzik
2007-06-08 20:41 ` Bartlomiej Zolnierkiewicz
2007-06-09 8:28 ` Jeff Garzik
2007-06-08 21:35 ` Alan Cox
2007-06-08 22:42 ` Bartlomiej Zolnierkiewicz
2007-06-08 22:35 ` Alan Cox
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=46641050.1030901@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=jirislaby@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ml@akana.de \
/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;
as well as URLs for NNTP newsgroup(s).