Linux IOMMU Development
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [git pull] IOMMU Fix for Linux v4.1-rc6
Date: Fri, 5 Jun 2015 11:20:18 +0200	[thread overview]
Message-ID: <20150605092018.GA25227@8bytes.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]

Hi Linus,

The following changes since commit c65b99f046843d2455aa231747b5a07a999a9f3d:

  Linux 4.1-rc6 (2015-05-31 19:01:07 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.1-rc6

for you to fetch changes up to 2d0ec7a19b5796aa958636eeeff072b506460501:

  Revert "iommu/amd: Don't allocate with __GFP_ZERO in alloc_coherent" (2015-06-02 08:46:32 +0200)

----------------------------------------------------------------
IOMMU Fix for Linux v4.1-rc6

Only one patch:

	* Revert "iommu/amd: Don't allocate with __GFP_ZERO in alloc_coherent"
	  This patch caused problems with some drivers, so it is better
	  to revert it now until the drivers have been fixed.

----------------------------------------------------------------
Joerg Roedel (1):
      Revert "iommu/amd: Don't allocate with __GFP_ZERO in alloc_coherent"

 drivers/iommu/amd_iommu.c | 1 +
 1 file changed, 1 insertion(+)

Please pull.

Thanks,

	Joerg


[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



                 reply	other threads:[~2015-06-05  9:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150605092018.GA25227@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox