Date: Tue, 9 Jan 2018 15:04:17 -0500
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: christian.koenig@amd.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] swiotlb: suppress warning when __GFP_NOWARN is set v5
Message-ID: <20180109200417.GB19756@char.us.oracle.com>
References: <20180104132419.24536-1-christian.koenig@amd.com>
 <20180104132919.GA7213@infradead.org>
 <7e470dfb-563f-2de4-7247-2949a528c6f6@gmail.com>
 <20180109194755.GA7283@infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <20180109194755.GA7283@infradead.org>
User-Agent: Mutt/1.8.3 (2017-05-23)
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org

On Tue, Jan 09, 2018 at 11:47:55AM -0800, Christoph Hellwig wrote:
> On Thu, Jan 04, 2018 at 02:49:21PM +0100, Christian K?nig wrote:
> > I perfectly agree on that, but this is for stable kernel backports. Because
> > of this I want to keep the footprint as low as possible.
> > 
> > When your patchset to clean that up lands for 4.16 I have no problem
> > changing that.
> > 
> > But till then I think we should just work on suppress the warning for now.
> 
> Oh well.  If Konrad is fine with that I'll stick it in front of my
> swiotlb series (the next post is going to be split) with a stable tag,
> so everything is well integrated.

Totally. Thanks for taking care of it - been slammed with x86 architecture craziness.