public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Jeff Garzik <jgarzik@pobox.com>,
	mike.miller@hp.com, akpm@osdl.org, axboe@suse.de,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: DMA mapping (was Re: [PATCH] cciss 2.6; replaces DMA masks with kernel defines)
Date: Fri, 10 Jun 2005 19:17:13 -0400	[thread overview]
Message-ID: <1118445434.6423.133.camel@mindpipe> (raw)
In-Reply-To: <20050610213003.GI24611@parcelfarce.linux.theplanet.co.uk>

On Fri, 2005-06-10 at 22:30 +0100, Matthew Wilcox wrote:
> On Fri, Jun 10, 2005 at 05:17:32PM -0400, Lee Revell wrote:
> > OK, this covers the drivers I know.  I didn't make any attempt to check
> > them all.
> 
> I know of two others ...
> 
> sym2 has:
> #define DMA_DAC_MASK    0x000000ffffffffffULL /* 40-bit */
> 
> and aic7xxx has:
>         const uint64_t   mask_39bit = 0x7FFFFFFFFFULL;
> 
> Would you mind respinning your patch to include these?
> 

I'm grepping the drivers, and what a mess.  This will be a nice cleanup.

Why would someone use 0xFFFFffff?

Lee


  parent reply	other threads:[~2005-06-10 23:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10 14:34 [PATCH] cciss 2.6; replaces DMA masks with kernel defines mike.miller
2005-06-10 16:55 ` Jeff Garzik
2005-06-10 20:39   ` DMA mapping (was Re: [PATCH] cciss 2.6; replaces DMA masks with kernel defines) Lee Revell
2005-06-10 20:45     ` Arjan van de Ven
2005-06-10 20:49       ` Lee Revell
2005-06-11 18:32         ` jgarzik
2005-06-13  2:58           ` Jeff Garzik
2005-06-10 20:59       ` Lee Revell
2005-06-10 21:17       ` Lee Revell
2005-06-10 21:30         ` Matthew Wilcox
2005-06-10 23:08           ` Lee Revell
2005-06-11 13:54             ` Matthew Wilcox
2005-06-15 18:19               ` Lee Revell
2005-06-10 23:17           ` Lee Revell [this message]
2005-06-11 15:39             ` Pavel Machek

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=1118445434.6423.133.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mike.miller@hp.com \
    /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