From: Matthew Wilcox <matthew@wil.cx>
To: linas <linas@austin.ibm.com>
Cc: James.Bottomley@steeleye.com, brking@us.ibm.com, gregkh@suse.de,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] PCI Error Recovery: Symbios SCSI device driver
Date: Wed, 18 Jan 2006 10:07:16 -0700 [thread overview]
Message-ID: <20060118170716.GA9569@parisc-linux.org> (raw)
In-Reply-To: <20060118165345.GA31920@austin.ibm.com>
On Wed, Jan 18, 2006 at 10:53:45AM -0600, linas wrote:
> Hi James,
Actually, I'm the sym2 maintainer.
> +static void sym_eeh_timeout(u_long p)
Please don't propagate more uses of this u_long crap. I haven't got
rid of all of them, but there's no need to add more.
> @@ -1630,6 +1682,8 @@ static struct Scsi_Host * __devinit sym_
> np->maxoffs = dev->chip.offset_max;
> np->maxburst = dev->chip.burst_max;
> np->myaddr = dev->host_id;
> + np->s.io_state = pci_channel_io_normal;
> + np->s.io_reset_wait = NULL;
Is there a good reason to put them in the 's'? It's really a dirty
hack.
> +/* ------------- PCI Error Recovery infrastructure -------------- */
> +/** sym2_io_error_detected() is called when PCI error is detected */
> +static pci_ers_result_t sym2_io_error_detected (struct pci_dev *pdev, pci_channel_state_t state)
> +{
> + struct sym_hcb *np = pci_get_drvdata(pdev);
> +
> + np->s.io_state = state;
> + // XXX If slot is permanently frozen, then what?
> + // Should we scsi_remove_host() maybe ??
> +
> + /* Request a slot slot reset. */
> + return PCI_ERS_RESULT_NEED_RESET;
> +}
Don't use C99 comments, don't put a space between the function name and
the opening bracket, and don't exceed 80 columns.
> +/** sym2_io_slot_reset is called when the pci bus has been reset.
> + * Restart the card from scratch. */
kerneldoc style comment, but not in kerneldoc format.
> + /* Perform host reset only on one instance of the card */
> + if (0 == PCI_FUNC (pdev->devfn))
I really hate "if (constant == variable)".
next prev parent reply other threads:[~2006-01-18 17:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 16:53 [PATCH] PCI Error Recovery: Symbios SCSI device driver linas
2006-01-18 17:07 ` Matthew Wilcox [this message]
2006-01-18 17:54 ` linas
-- strict thread matches above, loose matches on Subject: below --
2006-02-02 20:15 Linas Vepstas
2006-09-21 23:13 [PATCH]: " Linas Vepstas
2006-09-21 23:13 ` Linas Vepstas
2006-09-22 22:06 ` Luca
2006-09-22 22:06 ` Luca
2006-09-22 23:32 ` Linas Vepstas
2006-09-22 23:32 ` Linas Vepstas
2006-09-22 23:39 ` Randy.Dunlap
2006-09-22 23:39 ` Randy.Dunlap
2006-09-22 23:39 ` Randy.Dunlap
2006-09-22 23:50 ` Linas Vepstas
2006-09-22 23:50 ` Linas Vepstas
2006-09-23 0:57 ` Randy.Dunlap
2006-09-23 0:57 ` Randy.Dunlap
2006-09-23 0:57 ` Randy.Dunlap
2006-10-20 18:05 Linas Vepstas
2006-10-31 18:55 ` Matthew Wilcox
2006-10-31 19:24 ` James Bottomley
2006-10-31 22:26 ` Linas Vepstas
2006-10-31 23:13 ` Linas Vepstas
2006-11-02 4:46 ` Grant Grundler
2006-11-02 4:56 ` Matthew Wilcox
2007-07-02 18:39 Linas Vepstas
2007-07-02 18:39 ` Linas Vepstas
2007-07-05 18:28 ` Andrew Morton
2007-07-05 18:28 ` Andrew Morton
2007-07-05 18:28 ` Andrew Morton
2007-07-05 18:54 ` Matthew Wilcox
2007-07-05 18:54 ` Matthew Wilcox
2007-08-02 22:53 ` Linas Vepstas
2007-08-02 22:53 ` Linas Vepstas
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=20060118170716.GA9569@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@steeleye.com \
--cc=brking@us.ibm.com \
--cc=gregkh@suse.de \
--cc=linas@austin.ibm.com \
--cc=linux-scsi@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 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.