From: Jeff Garzik <jgarzik@pobox.com>
To: "Moore, Eric Dean" <Emoore@lsil.com>
Cc: linux-scsi@vger.kernel.org, James.Bottomley@steeleye.com,
ak@suse.de, Alexander.Stohr@gmx.de, rddunlap@osdl.org
Subject: Re: [PATCH 2.6 ] MPT Fusion driver 3.01.02 update
Date: Wed, 17 Mar 2004 15:20:33 -0500 [thread overview]
Message-ID: <4058B311.1010502@pobox.com> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57040DB25E@exa-atlanta.se.lsil.com>
Moore, Eric Dean wrote:
> This is an update for the MPT Fusion drivers 2.6 kernel.
> Version 3.01.02.
>
> Changelog:
>
> (1) Andi Kleen[ak@suse.de]
> put warning "Device (0:0:0) reported QUEUE_FULL!" into debug messages
>
> (2) Alexander Stohr[Alexander.Stohr@gmx.de]
> fix warnings from mptscsih_setup when driver isn't compiled as module
>
> (3) Randy.Dunlap[rddunlap@osdl.org]
> Remove unnecessary min/max macros and change calls to
> use kernel.h macros instead.
Here are some wrappers to remove:
static inline void CHIPREG_PIO_WRITE32(volatile u32 *a, u32 v)
{
outl(v, (unsigned long)a);
}
static inline u32 CHIPREG_PIO_READ32(volatile u32 *a)
{
return inl((unsigned long)a);
}
Also, I'm not sure about these wrappers, but it's mainly as style issue
due to the "if (PortIo)" test. You should remove the 'volatile'
markers, at least.
static inline u32 CHIPREG_READ32(volatile u32 *a)
{
if (PortIo)
return inl((unsigned long)a);
else
return readl(a);
}
static inline void CHIPREG_WRITE32(volatile u32 *a, u32 v)
{
if (PortIo)
outl(v, (unsigned long)a);
else
writel(v, a);
}
next prev parent reply other threads:[~2004-03-17 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 19:43 [PATCH 2.6 ] MPT Fusion driver 3.01.02 update Moore, Eric Dean
2004-03-17 20:20 ` Jeff Garzik [this message]
2004-03-18 1:09 ` Andi Kleen
2004-03-18 1:38 ` Moore, Eric Dean
2004-03-18 1:58 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-03-17 22:02 Moore, Eric Dean
2004-03-17 22:15 ` Jeff Garzik
2004-03-17 23:49 Moore, Eric Dean
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=4058B311.1010502@pobox.com \
--to=jgarzik@pobox.com \
--cc=Alexander.Stohr@gmx.de \
--cc=Emoore@lsil.com \
--cc=James.Bottomley@steeleye.com \
--cc=ak@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=rddunlap@osdl.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