From: Jes Sorensen <jes@wildopensource.com>
To: Matthew Wilcox <matthew@wil.cx>
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: 07 Mar 2005 09:27:17 -0500 [thread overview]
Message-ID: <yq04qfnedkq.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <20050307123739.GC28741@parcelfarce.linux.theplanet.co.uk>
>>>>> "Matthew" == Matthew Wilcox <matthew@wil.cx> writes:
Matthew> 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
>> It's ugly and really serves no purpose except for obfuscation.
Matthew> We've had drivers with typos. Missing one f suddenly causes
Matthew> all your memory to come from ZONE_DMA. Having an extra f
Matthew> causes your driver to work ... most of the time on machines
Matthew> with >4GB ram. Sure, your driver doesn't, but when looking
Matthew> over a lot of drivers, it's easier if everyone's using the
Matthew> same macros.
If these were the only two masks ever used I'd agree with you. However
there's several other in use and more will probably be added, so we're
going to end up with drivers sometimes using constants and other times
hex values causing an even bigger mess ;-(
Cheers,
Jes
next prev parent reply other threads:[~2005-03-07 14:27 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
2005-03-07 14:27 ` Jes Sorensen [this message]
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=yq04qfnedkq.fsf@jaguar.mkp.net \
--to=jes@wildopensource.com \
--cc=James.Bottomley@SteelEye.com \
--cc=domen@coderock.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--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