From: David Rientjes <rientjes@google.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mel Gorman <mel@csn.ul.ie>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Make GFP_DMA allocations w/o ZONE_DMA emit a warning instead of failing
Date: Wed, 1 Jun 2011 12:09:12 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1106011205410.17065@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1106012043080.3078@ionos>
On Wed, 1 Jun 2011, Thomas Gleixner wrote:
> > That is NOT an unreasonable request, but it seems that its far too much
> > to ask of you.
>
> Full ack.
>
> David,
>
> stop that nonsense already. You changed the behaviour and broke stuff
> which was working fine before for whatever reason. That behaviour was
> in the kernel for ages and we tolerated the abuse.
>
Did I nack this patch and not realize it?
Does my patch fix the warning for pxaficp_ir that would still be emitted
with this patch? If the driver uses GFP_DMA and nobody from the arm side
is prepared to remove it yet, then I'd suggest merging my patch until that
can be determined. Otherwise, you have no guarantees about where the
memory is actually coming from.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-01 19:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 10:04 Dmitry Eremin-Solenikov
2011-06-01 12:38 ` KOSAKI Motohiro
2011-06-01 15:07 ` Dmitry Eremin-Solenikov
2011-06-01 17:23 ` David Rientjes
2011-06-01 18:19 ` Russell King - ARM Linux
2011-06-01 18:55 ` Thomas Gleixner
2011-06-01 19:09 ` David Rientjes [this message]
2011-06-01 19:46 ` Thomas Gleixner
2011-06-10 7:38 ` KOSAKI Motohiro
2011-06-10 7:43 ` Andrew Morton
2011-06-10 7:52 ` KOSAKI Motohiro
2011-06-10 8:11 ` Dmitry Eremin-Solenikov
2011-06-10 9:12 ` Russell King - ARM Linux
2011-06-10 18:54 ` David Rientjes
2011-06-10 18:58 ` Russell King - ARM Linux
2011-06-10 22:01 ` David Rientjes
2011-06-10 22:07 ` Russell King - ARM Linux
2011-06-10 22:16 ` David Rientjes
2011-06-10 22:20 ` Russell King - ARM Linux
2011-06-10 22:30 ` David Rientjes
2011-06-11 9:45 ` Catalin Marinas
2011-06-11 17:18 ` Robert Hancock
2011-06-12 13:48 ` Russell King - ARM Linux
2011-06-01 18:30 ` Dmitry Eremin-Solenikov
2011-06-01 18:42 ` David Rientjes
2011-06-02 21:46 ` Pavel Machek
2011-06-12 11:07 ` Rafael J. Wysocki
2011-06-12 11:33 ` Cyril Hrubis
2011-06-12 11:39 ` Rafael J. Wysocki
2011-06-10 22:24 ` Linus Torvalds
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=alpine.DEB.2.00.1106011205410.17065@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=dbaryshkov@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=mel@csn.ul.ie \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
/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