From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH RFC] dma-direct: Try reallocation with GFP_DMA32 if possible
Date: Fri, 20 Apr 2018 12:06:25 +0200 [thread overview]
Message-ID: <20180420100625.GA6728@lst.de> (raw)
In-Reply-To: <s5hfu3qw659.wl-tiwai-l3A5Bk7waGM@public.gmane.org>
On Fri, Apr 20, 2018 at 11:58:58AM +0200, Takashi Iwai wrote:
> It's because it's written on the tree with another fix patch I sent
> beforehand ("[PATCH 1/2] dma-direct: Don't repeat allocation for no-op
> GFP_DMA").
>
> Could you check that one at first? I'm fine to rebase and resubmit
> this one, if still preferred, though.
That one looks fine, too. I'll add it to my patch queue.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] dma-direct: Try reallocation with GFP_DMA32 if possible
Date: Fri, 20 Apr 2018 12:06:25 +0200 [thread overview]
Message-ID: <20180420100625.GA6728@lst.de> (raw)
In-Reply-To: <s5hfu3qw659.wl-tiwai@suse.de>
On Fri, Apr 20, 2018 at 11:58:58AM +0200, Takashi Iwai wrote:
> It's because it's written on the tree with another fix patch I sent
> beforehand ("[PATCH 1/2] dma-direct: Don't repeat allocation for no-op
> GFP_DMA").
>
> Could you check that one at first? I'm fine to rebase and resubmit
> this one, if still preferred, though.
That one looks fine, too. I'll add it to my patch queue.
next prev parent reply other threads:[~2018-04-20 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 15:18 [PATCH RFC] dma-direct: Try reallocation with GFP_DMA32 if possible Takashi Iwai
[not found] ` <20180416151819.27520-1-tiwai-l3A5Bk7waGM@public.gmane.org>
2018-04-20 9:47 ` Christoph Hellwig
2018-04-20 9:47 ` Christoph Hellwig
[not found] ` <20180420094702.GA6530-jcswGhMUV9g@public.gmane.org>
2018-04-20 9:58 ` Takashi Iwai
2018-04-20 9:58 ` Takashi Iwai
[not found] ` <s5hfu3qw659.wl-tiwai-l3A5Bk7waGM@public.gmane.org>
2018-04-20 10:06 ` Christoph Hellwig [this message]
2018-04-20 10:06 ` Christoph Hellwig
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=20180420100625.GA6728@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tiwai-l3A5Bk7waGM@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.