public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>,
	scott.feldman@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add PCI_DMA_{64,32}BIT constants
Date: Fri, 26 Mar 2004 20:21:02 -0500	[thread overview]
Message-ID: <4064D6FE.7000506@pobox.com> (raw)
In-Reply-To: <20040327004842.GA13611@kroah.com>

Greg KH wrote:
> On Fri, Mar 26, 2004 at 07:41:22PM -0500, Jeff Garzik wrote:
> 
>>Greg KH wrote:
>>
>>>On Tue, Mar 23, 2004 at 12:23:05AM -0500, Jeff Garzik wrote:
>>>
>>>
>>>>Been meaning to do this for ages...
>>>>
>>>>Another one for the janitors.
>>>>
>>>>Please do a
>>>>
>>>>	bk pull bk://kernel.bkbits.net/jgarzik/pci-dma-mask-2.6
>>>>
>>>>This will update the following files:
>>>
>>>
>>>Nice, I've pulled this to my pci tree and will forward it on to Linus in
>>>the next round of pci patches after 2.6.5 is out.
>>
>>Yeah well...  in the intervening time, somebody on IRC commented
>>
>>"so what is so PCI-specific about those constants?"
>>
>>They probably ought to be DMA_{32,64}BIT_MASK or somesuch.
> 
> 
> Heh, ok, care to make up another patch for this?  :)

Yeah, but not at the moment :)  So just drop it for now, I suppose.

	Jeff





  reply	other threads:[~2004-03-27  1:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23  5:23 [PATCH] add PCI_DMA_{64,32}BIT constants Jeff Garzik
2004-03-27  0:29 ` Greg KH
2004-03-27  0:41   ` Jeff Garzik
2004-03-27  0:48     ` Greg KH
2004-03-27  1:21       ` Jeff Garzik [this message]
2004-03-30  6:36 ` Randy.Dunlap
2004-03-30 22:35   ` Jeff Garzik
2004-03-31  1:26   ` Greg KH
2004-03-31  3:58     ` Randy.Dunlap
2004-03-31 22:49       ` Greg KH

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=4064D6FE.7000506@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott.feldman@intel.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