From: Joerg Roedel <jroedel@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: iommu <iommu@lists.linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iommu/amd: fix a crash in iova_magazine_free_pfns
Date: Mon, 22 Jul 2019 15:30:53 +0200 [thread overview]
Message-ID: <20190722133053.GI19068@suse.de> (raw)
In-Reply-To: <CAHk-=wgwd9vT1h7jKMU_E4ae2QLFFH69UxcXpO3J9YqEApdUNg@mail.gmail.com>
Hi Linus,
On Sun, Jul 21, 2019 at 09:58:04AM -0700, Linus Torvalds wrote:
> This one seems to have fallen through the cracks.
>
> Applied directly.
Thanks!
> Maybe it's hiding in some fixes tree that I haven't gotten a pull
> request for yet?
No, I havn't had it applied anywhere yet. I usually don't pay close
attention to patches sent to me during the merge window, as I won't
update my tree anyway before -rc1.
I only take care of important fixes, but this one seems to have
fallen through my heuristic. Thanks for applying it directly.
Regards,
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <jroedel@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Qian Cai <cai@lca.pw>, Christoph Hellwig <hch@lst.de>,
iommu <iommu@lists.linux-foundation.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iommu/amd: fix a crash in iova_magazine_free_pfns
Date: Mon, 22 Jul 2019 15:30:53 +0200 [thread overview]
Message-ID: <20190722133053.GI19068@suse.de> (raw)
In-Reply-To: <CAHk-=wgwd9vT1h7jKMU_E4ae2QLFFH69UxcXpO3J9YqEApdUNg@mail.gmail.com>
Hi Linus,
On Sun, Jul 21, 2019 at 09:58:04AM -0700, Linus Torvalds wrote:
> This one seems to have fallen through the cracks.
>
> Applied directly.
Thanks!
> Maybe it's hiding in some fixes tree that I haven't gotten a pull
> request for yet?
No, I havn't had it applied anywhere yet. I usually don't pay close
attention to patches sent to me during the merge window, as I won't
update my tree anyway before -rc1.
I only take care of important fixes, but this one seems to have
fallen through my heuristic. Thanks for applying it directly.
Regards,
Joerg
next prev parent reply other threads:[~2019-07-22 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 16:17 [PATCH v2] iommu/amd: fix a crash in iova_magazine_free_pfns Qian Cai
2019-07-11 16:17 ` Qian Cai
2019-07-11 16:21 ` Christoph Hellwig
2019-07-11 16:21 ` Christoph Hellwig
2019-07-21 16:58 ` Linus Torvalds
2019-07-21 16:58 ` Linus Torvalds
2019-07-22 13:30 ` Joerg Roedel [this message]
2019-07-22 13:30 ` Joerg Roedel
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=20190722133053.GI19068@suse.de \
--to=jroedel@suse.de \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.