From: Christoph Hellwig <hch@lst.de>
To: x86@kernel.org
Cc: Evgeniy Didin <Evgeniy.Didin@synopsys.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: tip/x86/dma fix for arc and s390 (at least)
Date: Wed, 28 Mar 2018 15:35:34 +0200 [thread overview]
Message-ID: <20180328133535.17302-1-hch@lst.de> (raw)
Hi all,
this restores previous __GFP_ZERO passthrough behavior for now as arc and
s390 rely on it. Needs more work to sort out the API mess in the long run.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: Evgeniy Didin
<Evgeniy.Didin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Sebastian Ott
<sebott-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: tip/x86/dma fix for arc and s390 (at least)
Date: Wed, 28 Mar 2018 15:35:34 +0200 [thread overview]
Message-ID: <20180328133535.17302-1-hch@lst.de> (raw)
Hi all,
this restores previous __GFP_ZERO passthrough behavior for now as arc and
s390 rely on it. Needs more work to sort out the API mess in the long run.
next reply other threads:[~2018-03-28 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 13:35 Christoph Hellwig [this message]
2018-03-28 13:35 ` tip/x86/dma fix for arc and s390 (at least) Christoph Hellwig
2018-03-28 13:35 ` [PATCH] dma-mapping: don't clear GFP_ZERO in dma_alloc_attrs Christoph Hellwig
2018-03-28 13:35 ` Christoph Hellwig
2018-03-28 15:12 ` Evgeniy Didin
2018-03-28 15:12 ` Evgeniy Didin
2018-03-28 15:12 ` Evgeniy Didin
2018-04-09 10:52 ` dma-mapping: clear harmful GFP_* flags in common code Alexey Brodkin
2018-04-09 10:52 ` Alexey Brodkin
2018-04-09 10:52 ` Alexey Brodkin
2018-03-28 15:40 ` [tip:x86/dma] dma-mapping: Don't clear GFP_ZERO in dma_alloc_attrs tip-bot for 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=20180328133535.17302-1-hch@lst.de \
--to=hch@lst.de \
--cc=Evgeniy.Didin@synopsys.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebott@linux.vnet.ibm.com \
--cc=x86@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 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.