From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 5/5] sil24: make error_intr less verbose
Date: Wed, 16 Nov 2005 07:38:52 -0500 [thread overview]
Message-ID: <437B285C.8020809@pobox.com> (raw)
In-Reply-To: <20051116080935.GE22807@htj.dyndns.org>
Tejun Heo wrote:
> sil24_error_intr is too verbose. Shut it up.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
>
> Index: work/drivers/scsi/sata_sil24.c
> ===================================================================
> --- work.orig/drivers/scsi/sata_sil24.c 2005-11-16 17:05:19.000000000 +0900
> +++ work/drivers/scsi/sata_sil24.c 2005-11-16 17:08:05.000000000 +0900
> @@ -678,9 +678,9 @@ static void sil24_error_intr(struct ata_
> if (serror)
> writel(serror, port + PORT_SERROR);
>
> - printk(KERN_ERR DRV_NAME " ata%u: error interrupt on port%d\n"
> - " stat=0x%x irq=0x%x cmd_err=%d sstatus=0x%x serror=0x%x\n",
> - ap->id, ap->port_no, slot_stat, irq_stat, cmd_err, sstatus, serror);
> + DPRINTK("ata%u: error interrupt on port%d\n"
> + " stat=0x%x irq=0x%x cmd_err=%d sstatus=0x%x serror=0x%x\n",
> + ap->id, ap->port_no, slot_stat, irq_stat, cmd_err, sstatus, serror);
Mild NAK.
I am grappling with this on AHCI too :) This is because ATA_ERR is much
more common on ATAPI, yes?
My preferred change would be
if ((class != ATA_DEV_ATAPI) ||
(sil24_cmd_err > PORT_CERR_SDB))
printk()
so that truly uncommon errors are always printed, but users logs are not
spammed.
Another option is to do
if (ata_ratelimit())
printk()
Regards,
Jeff
next prev parent reply other threads:[~2005-11-16 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 8:09 [PATCH 5/5] sil24: make error_intr less verbose Tejun Heo
2005-11-16 12:38 ` Jeff Garzik [this message]
2005-11-16 13:27 ` Tejun Heo
2005-11-16 18:35 ` Edward Falk
2005-11-17 3:03 ` Albert Lee
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=437B285C.8020809@pobox.com \
--to=jgarzik@pobox.com \
--cc=htejun@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).