mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Andi Kleen <ak@suse.de>
Cc: Matthew Wilcox <willy@debian.org>, linux-kernel@vger.kernel.org
Subject: Re: Proposal: Eliminate GFP_DMA
Date: Fri, 28 Feb 2003 14:12:34 +0000	[thread overview]
Message-ID: <20030228141234.H23865@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <p73heao7ph2.fsf@amdsimf.suse.de>; from ak@suse.de on Fri, Feb 28, 2003 at 09:56:41AM +0100

On Fri, Feb 28, 2003 at 09:56:41AM +0100, Andi Kleen wrote:
> Matthew Wilcox <willy@debian.org> writes:
> > -
> > +#define GFP_ATOMIC_DMA (GFP_ATOMIC | __GFP_DMA)
> > +#define GFP_KERNEL_DMA (GFP_KERNEL | __GFP_DMA)
> > 
> > combined with changing some users to use __GFP_DMA if they really do mean
> > the bitmask.  Comments?
> 
> Sounds like a good 2.7.x early project. Currently we still have too much
> driver breakage for the next release to break even more right now.

i'm not the kind of person who just changes the header file and breaks all
the drivers.  plan:

 - Add the GFP_ATOMIC_DMA & GFP_KERNEL_DMA definitions
 - Change the drivers
 - Delete the GFP_DMA definition

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  reply	other threads:[~2003-02-28 14:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030228064631.G23865@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
2003-02-28  8:56 ` Andi Kleen
2003-02-28 14:12   ` Matthew Wilcox [this message]
2003-02-28 15:24     ` Alan Cox
2003-02-28 14:34       ` Matthew Wilcox
2003-02-28 15:55         ` Alan Cox
2003-02-28 14:56           ` Andi Kleen
2003-02-28 15:25             ` Jeff Garzik
2003-02-28 15:30               ` Andi Kleen
2003-02-28 15:34               ` Martin J. Bligh
2003-02-28 15:49                 ` Eli Carter
2003-02-28 16:03                   ` Russell King
2003-02-28 16:45                 ` Alan Cox
2003-02-28 15:31             ` Arjan van de Ven
2003-03-04 17:56           ` Rogier Wolff
2003-03-04 23:09             ` Alan Cox
2003-03-05  7:43               ` Rogier Wolff
2003-03-05 13:53                 ` Alan Cox
2003-02-28 15:44       ` Dmitry A. Fedorov
2003-02-28 15:58         ` Jeff Garzik
2003-02-28 18:17           ` Deepak Saxena
2003-02-28 18:27             ` Deepak Saxena
2003-02-28 19:52             ` Russell King
     [not found]           ` <mailman.1046456425.7772.linux-kernel2news@redhat.com>
2003-02-28 20:51             ` Pete Zaitcev
2003-02-28 22:11               ` Russell King
2003-02-28 16:05         ` Russell King
2003-02-28 17:27           ` Ivan Kokshaysky
2003-02-28 17:45         ` Alan Cox
2003-02-28  6:46 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=20030228141234.H23865@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®