From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
stable <stable@kernel.org>, Robert Hancock <hancockrwd@gmail.com>
Subject: Re: [PATCH #upstream-fixes] sata_nv: use ata_pci_sff_activate_host() instead of ata_host_activate()
Date: Fri, 14 May 2010 17:12:33 -0400 [thread overview]
Message-ID: <4BEDBCC1.5080700@garzik.org> (raw)
In-Reply-To: <4BED1C82.10102@kernel.org>
On 05/14/2010 05:48 AM, Tejun Heo wrote:
> sata_nv was incorrectly using ata_host_activate() instead of
> ata_pci_sff_activate_host() leading to IRQ assignment failure in
> legacy mode. Fix it.
>
> Signed-off-by: Tejun Heo<tj@kernel.org>
> Cc: Robert Hancock<hancockr@shaw.ca>
> Cc: stable@kernel.org
> ---
> drivers/ata/sata_nv.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> Index: ata/drivers/ata/sata_nv.c
> ===================================================================
> --- ata.orig/drivers/ata/sata_nv.c
> +++ ata/drivers/ata/sata_nv.c
> @@ -2479,8 +2479,7 @@ static int nv_init_one(struct pci_dev *p
> }
>
> pci_set_master(pdev);
> - return ata_host_activate(host, pdev->irq, ipriv->irq_handler,
> - IRQF_SHARED, ipriv->sht);
> + return ata_pci_sff_activate_host(host, ipriv->irq_handler, ipriv->sht);
hmmmm. I agree 100% with this patch, but is it a recent regression?
At -rc7, we are trying hard to only include fixes for regressions.
Around -rc1, I would stuff this into #upstream-fixes without hesitation.
But now, I'm thinking #upstream.
Jeff
next prev parent reply other threads:[~2010-05-14 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 9:48 [PATCH #upstream-fixes] sata_nv: use ata_pci_sff_activate_host() instead of ata_host_activate() Tejun Heo
2010-05-14 21:12 ` Jeff Garzik [this message]
2010-05-14 22:05 ` Tejun Heo
2010-05-15 2:07 ` Jeff Garzik
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=4BEDBCC1.5080700@garzik.org \
--to=jeff@garzik.org \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.