linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Tejun Heo <htejun@gmail.com>, Alan Cox <alan@redhat.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: sata_mv fixes:  coding style preference?
Date: Wed, 28 Nov 2007 09:19:20 -0500	[thread overview]
Message-ID: <474D78E8.8040806@rtr.ca> (raw)
In-Reply-To: <474D3D8E.7030207@pobox.com>

(adding linux-ide to CC:)

Jeff Garzik wrote:
> Mark Lord wrote:
>
>> Below, I used inline functions to calculate the correct reg offsets
>> so that the rest of the code doesn't need any special if-stmts.
>> But another way to do it would be to just store the correct offsets
>> as new fields within the mv_host_priv struct.  I suspect that method
>> would be better.
> 
> Yes, store the offsets, you shouldn't need to call a function to 
> calculate the same value over and over again.  Simple, no branches added 
> to the code, ...
..

Good, so we all agree on that!

And as it turns out, this patch (or the better version coming later)
fixes both of the Marvell 7042 problems reported here a couple of weeks ago:

1:  Tom Morrison "hang with large file operations".
2.  Hein-Pieter van Braam "PCI ERROR; PCI IRQ reason=0x00000000 highpoint rocketraid 2300 pci-e"

Tom has confirmed the fix, and I'm waiting to hear back from Hein-Pieter
even though I now have identical hardware here as what he has.

Jeff:  This fix (one I reissue it) should go upstream for 2.6.24, if possible.

Right now the driver is guaranteed to fail on 7042, since it is hitting
reserved PCI addresses instead of valid registers.

Not a regression though, so your call.
But it does fix reported bugs, and really cannot hurt anything.

Cheers

       reply	other threads:[~2007-11-28 14:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <474CC20D.6010800@rtr.ca>
     [not found] ` <474D3D8E.7030207@pobox.com>
2007-11-28 14:19   ` Mark Lord [this message]
2007-11-28 16:00     ` sata_mv fixes: coding style preference? 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=474D78E8.8040806@rtr.ca \
    --to=liml@rtr.ca \
    --cc=alan@redhat.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.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).