public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Tue, 9 Jan 2018 15:04:17 -0500	[thread overview]
Message-ID: <20180109200417.GB19756@char.us.oracle.com> (raw)
In-Reply-To: <20180109194755.GA7283@infradead.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.

  reply	other threads:[~2018-01-09 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 13:24 [PATCH] swiotlb: suppress warning when __GFP_NOWARN is set v5 Christian König
2018-01-04 13:29 ` Christoph Hellwig
2018-01-04 13:49   ` Christian König
2018-01-09 19:47     ` Christoph Hellwig
2018-01-09 20:04       ` Konrad Rzeszutek Wilk [this message]
2018-01-09 21:12         ` Christoph Hellwig
2018-01-09 21:23           ` Konrad Rzeszutek Wilk

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=20180109200417.GB19756@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=christian.koenig@amd.com \
    --cc=hch@infradead.org \
    --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