mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: David Rientjes <rientjes@google.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
	Samuel Ortiz <samuel@sortiz.org>,
	Eric Miao <eric.y.miao@gmail.com>,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: IrDA driver fails on PXA255
Date: Wed, 1 Jun 2011 16:50:16 +0100	[thread overview]
Message-ID: <20110601155016.GM3660@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110601075420.GB3660@n2100.arm.linux.org.uk>

On Wed, Jun 01, 2011 at 08:54:20AM +0100, Russell King - ARM Linux wrote:
> On Tue, May 31, 2011 at 03:11:40PM -0700, David Rientjes wrote:
> > The restriction isn't new: GFP_DMA only makes sense with CONFIG_ZONE_DMA.  
> > The fact that the page allocator completely ignored GFP_DMA in the past 
> > for CONFIG_ZONE_DMA=n doesn't change that.  That's obviously error prone 
> > since it will return memory from anywhere simply because of the fact that 
> > it is an invalid configuration.
> 
> Your approach to this is wrong.  Make it warn for one release.  Give
> people a chance to fix things before they become a regression.  Then
> make it a hard failure.

And to prove that its not just this driver, I've now received a report
that it fails with the CF PATA driver on Zaurus.  Should we make the
PATA subsystem select CONFIG_ZONE_DMA too, or should we give people
some grace period to fix the drivers as _everyone_ except you is
suggesting.

Please do the sensible thing.  Make it warn for a release like everyone
is telling you to.

      reply	other threads:[~2011-06-01 15:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-28 20:57 Dmitry Eremin-Solenikov
2011-05-28 23:34 ` David Rientjes
2011-05-28 23:46   ` Russell King - ARM Linux
2011-05-29  2:22     ` David Rientjes
2011-05-29  7:25       ` Russell King - ARM Linux
2011-05-29 21:19         ` David Rientjes
2011-05-29 21:58           ` Russell King - ARM Linux
2011-05-31  5:01             ` David Rientjes
2011-05-29  8:36   ` Dmitry Eremin-Solenikov
2011-05-29 21:17     ` David Rientjes
2011-05-29 21:33       ` Dmitry Eremin-Solenikov
2011-05-29 21:56       ` Russell King - ARM Linux
2011-05-31  5:05         ` David Rientjes
2011-05-31  7:26           ` Russell King - ARM Linux
2011-05-31 20:03             ` David Rientjes
2011-05-31 21:00               ` Russell King - ARM Linux
2011-05-31 22:11                 ` David Rientjes
2011-06-01  7:54                   ` Russell King - ARM Linux
2011-06-01 15:50                     ` Russell King - ARM Linux [this message]

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=20110601155016.GM3660@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=dbaryshkov@gmail.com \
    --cc=eric.y.miao@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=rientjes@google.com \
    --cc=samuel@sortiz.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®