From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] AHCI: Make distinct names for ports in /proc/interrupts
Date: Mon, 29 Apr 2013 15:32:08 +0400 [thread overview]
Message-ID: <517E5A38.7050609@cogentembedded.com> (raw)
In-Reply-To: <20130429101237.GA27738@dhcp-26-207.brq.redhat.com>
Hello.
On 29-04-2013 14:12, Alexander Gordeev wrote:
> Currently all interrupts assigned to AHCI ports show up in
> '/proc/interrupts' as 'ahci'. This fix adds port numbers as
> suffixes and hence makes the descriptions distinct.
> Reported-by: Jan Beulich <JBeulich@suse.com>
> Signed-off-by: Alexander Gordeev <agordeev@redhat.com>
> ---
> drivers/ata/ahci.c | 6 ++++--
> drivers/ata/ahci.h | 1 +
> 2 files changed, 5 insertions(+), 2 deletions(-)
> diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
> index 3b9a7b1..dc5c1aa 100644
> --- a/drivers/ata/ahci.c
> +++ b/drivers/ata/ahci.c
> @@ -1146,10 +1146,12 @@ int ahci_host_activate(struct ata_host *host, int irq, unsigned int n_msis,
> return -EINVAL;
>
> for (i = 0; i < n_irqs; i++) {
> + struct ahci_port_priv *pp = host->ports[i]->private_data;
Empty line wouldn't hurt here, after declaration.
> + snprintf(pp->irq_desc, sizeof(pp->irq_desc),
> + "%s%d", dev_driver_string(host->dev), i);
> rc = devm_request_threaded_irq(host->dev, irq + i,
> ahci_multi_irqs_intr, ahci_port_thread_fn,
> - IRQF_SHARED, dev_driver_string(host->dev),
> - host->ports[i]);
> + IRQF_SHARED, pp->irq_desc, host->ports[i]);
> if (rc)
> goto out_free_irqs;
> }
WBR, Sergei
next prev parent reply other threads:[~2013-04-29 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 10:12 [PATCH] AHCI: Make distinct names for ports in /proc/interrupts Alexander Gordeev
2013-04-29 11:32 ` Sergei Shtylyov [this message]
2013-04-30 21:41 ` Jeff Garzik
2013-05-07 8:38 ` [PATCH v2] " Alexander Gordeev
2013-05-14 18:56 ` Tejun Heo
2013-05-14 19:41 ` Alexander Gordeev
2013-05-14 20:44 ` Tejun Heo
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=517E5A38.7050609@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=JBeulich@suse.com \
--cc=agordeev@redhat.com \
--cc=jgarzik@pobox.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