From: Matthew Wilcox <matthew@wil.cx>
To: Jes Sorensen <jes@wildopensource.com>
Cc: domen@coderock.org, James.Bottomley@SteelEye.com,
linux-scsi@vger.kernel.org, tklauser@nuerscht.ch
Subject: Re: [patch 10/11] drivers/scsi/: Use the DMA_{64,32}BIT_MASK constants
Date: Mon, 7 Mar 2005 12:37:39 +0000 [thread overview]
Message-ID: <20050307123739.GC28741@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <yq0ekerepaf.fsf@jaguar.mkp.net>
On Mon, Mar 07, 2005 at 05:14:16AM -0500, Jes Sorensen wrote:
> >>>>> "domen" == domen <domen@coderock.org> writes:
>
> domen> Use the DMA_{64,32}BIT_MASK constants from dma-mapping.h when
> domen> calling pci_set_dma_mask() or pci_set_consistent_dma_mask() See
> domen> http://marc.theaimsgroup.com/?t=108001993000001&r=1&w=2 for
> domen> details
>
> Why?
>
> It's ugly and really serves no purpose except for obfuscation.
We've had drivers with typos. Missing one f suddenly causes all your
memory to come from ZONE_DMA. Having an extra f causes your driver to
work ... most of the time on machines with >4GB ram. Sure, your driver
doesn't, but when looking over a lot of drivers, it's easier if everyone's
using the same macros.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-03-07 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 22:27 [patch 10/11] drivers/scsi/: Use the DMA_{64,32}BIT_MASK constants domen
2005-03-07 10:14 ` Jes Sorensen
2005-03-07 12:37 ` Matthew Wilcox [this message]
2005-03-07 14:27 ` Jes Sorensen
2005-03-07 14:36 ` Matthew Wilcox
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=20050307123739.GC28741@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=domen@coderock.org \
--cc=jes@wildopensource.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tklauser@nuerscht.ch \
/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