All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Tim Small <tim@buttersideup.com>, linux-ide@vger.kernel.org
Cc: tj@kernel.org
Subject: Re: [PATCH] sata_sil24: Identify which card suffered IRQ status error
Date: Tue, 22 Jul 2014 18:10:50 +0400	[thread overview]
Message-ID: <53CE70EA.7030600@cogentembedded.com> (raw)
In-Reply-To: <20140722132800.952BA60250@zebedee.buttersideup.com>

Hello.

On 07/22/2014 05:28 PM, Tim Small wrote:

> In machines with multiple Silicon Image 3124 and/or 3132 cards, there is no
> way to tell which card is the culprit when the sata_sil24 interrupt handler
> gets a bad status.

> Tested-by: tim@seoss.co.uk
> Signed-off-by: tim@seoss.co.uk

    Full name is required before email, and email should be enclosed in <>. 
Also, I guess you want the same email as the commit author and in the signoff? 
Use the From: line at the start of mail to override the one in the header. See 
Documentation/SubmittingPatches for more details...

[...]

> diff --git a/drivers/ata/sata_sil24.c b/drivers/ata/sata_sil24.c
> index 0534890..d81b20d 100644
> --- a/drivers/ata/sata_sil24.c
> +++ b/drivers/ata/sata_sil24.c
> @@ -1154,8 +1154,8 @@ static irqreturn_t sil24_interrupt(int irq, void *dev_instance)
>   	status = readl(host_base + HOST_IRQ_STAT);
>
>   	if (status == 0xffffffff) {
> -		printk(KERN_ERR DRV_NAME ": IRQ status == 0xffffffff, "
> -		       "PCI fault or device removal?\n");
> +		dev_err(host->dev, "IRQ status == 0xffffffff, "
> +			"PCI fault or device removal?\n");

    Don't break the string anymore please. I guess you haven't run the patch 
thru scripts/checkpatch.pl?

>   		goto out;
>   	}

WBR, Sergei


      parent reply	other threads:[~2014-07-22 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 13:28 [PATCH] sata_sil24: Identify which card suffered IRQ status error Tim Small
2014-07-22 14:09 ` Tejun Heo
2014-07-22 14:10 ` Sergei Shtylyov [this message]

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=53CE70EA.7030600@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=tim@buttersideup.com \
    --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.