From: Joerg Roedel <joro@8bytes.org>
To: Vijayanand Jitta <quic_vjitta@quicinc.com>
Cc: kernel-team@android.com, robin.murphy@arm.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
vjitta@codeaurora.org, will@kernel.org
Subject: Re: [REPOST PATCH v4] iommu: Fix potential use-after-free during probe
Date: Mon, 31 Jan 2022 16:31:11 +0100 [thread overview]
Message-ID: <YfgAv0N/iTU39Ve0@8bytes.org> (raw)
In-Reply-To: <1643613155-20215-1-git-send-email-quic_vjitta@quicinc.com>
On Mon, Jan 31, 2022 at 12:42:35PM +0530, Vijayanand Jitta wrote:
> drivers/iommu/iommu.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
Applied, thanks Vijayanand.
_______________________________________________
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 <joro@8bytes.org>
To: Vijayanand Jitta <quic_vjitta@quicinc.com>
Cc: robin.murphy@arm.com, will@kernel.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
kernel-team@android.com, vjitta@codeaurora.org
Subject: Re: [REPOST PATCH v4] iommu: Fix potential use-after-free during probe
Date: Mon, 31 Jan 2022 16:31:11 +0100 [thread overview]
Message-ID: <YfgAv0N/iTU39Ve0@8bytes.org> (raw)
In-Reply-To: <1643613155-20215-1-git-send-email-quic_vjitta@quicinc.com>
On Mon, Jan 31, 2022 at 12:42:35PM +0530, Vijayanand Jitta wrote:
> drivers/iommu/iommu.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
Applied, thanks Vijayanand.
next prev parent reply other threads:[~2022-01-31 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 7:12 [REPOST PATCH v4] iommu: Fix potential use-after-free during probe Vijayanand Jitta
2022-01-31 7:12 ` Vijayanand Jitta
2022-01-31 15:31 ` Joerg Roedel [this message]
2022-01-31 15:31 ` 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=YfgAv0N/iTU39Ve0@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_vjitta@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=vjitta@codeaurora.org \
--cc=will@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.