From: David Miller <davem@davemloft.net>
To: bzolnier@gmail.com
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cs5520: add missing IRQ setup for the second port
Date: Mon, 22 Jun 2009 16:31:36 -0700 (PDT) [thread overview]
Message-ID: <20090622.163136.246300819.davem@davemloft.net> (raw)
In-Reply-To: <200906221348.02632.bzolnier@gmail.com>
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Date: Mon, 22 Jun 2009 13:48:02 +0200
> From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> Subject: [PATCH] cs5520: add missing IRQ setup for the second port
>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> ---
> This is obviously correct regression fix. The only problem is that
> it cannot be applied under the new rigid policy before somebody with
> the hardware verifies it. This will only result in a needless delay
> in this case (IMHO a common sense works better than rigid policies).
Such hard rules don't apply to regression fixes. Patch
applied, thanks.
But I certainly would have required some positive testing for the
commit which introduced this problem!
I've added some verbosity to the commit message, so that people can
track where the problem was introduced, and exactly how this problem
arose, like so:
cs5520: add missing IRQ setup for the second port
This fixes a regression introduced by commit
86ccf37c6acd74cf7e4b7751ee045de19943c5a0 ("ide: remove pciirq argument
from ide_pci_setup_ports()")
ide_pci_setup_ports() would loop over the available ports, one
by one, recording IRQ numbers increasingly from the one passed
in as "pciirq". The conversion only assigned the initial port's
IRQ, 14, but left the second one not setup.
[ Make commit message more verbose -DaveM ]
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2009-06-22 23:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 11:48 Bartlomiej Zolnierkiewicz
2009-06-22 23:31 ` David Miller [this message]
2009-06-22 23:58 ` Frans Pop
2009-06-23 8:42 ` Alan Cox
2009-06-23 9:59 ` Bartlomiej Zolnierkiewicz
2009-06-23 15:33 ` Alan Cox
2009-06-23 23:44 ` David Miller
2009-06-24 9:22 ` Alan Cox
2009-06-24 9:36 ` David Miller
2009-06-23 0:30 ` Bartlomiej Zolnierkiewicz
2009-06-23 1:05 ` Bartlomiej Zolnierkiewicz
2009-06-23 4:16 ` David Miller
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=20090622.163136.246300819.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--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®