From: Joerg Roedel <joro@8bytes.org>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: stable@vger.kernel.org, iommu@lists.linux-foundation.org,
Ricardo Ribalda <ribalda@chromium.org>,
kernel@collabora.com, Will Deacon <will@kernel.org>,
Christoph Hellwig <hch@lst.de>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] iommu/dma: Fix leak in non-contiguous API
Date: Mon, 26 Jul 2021 14:27:29 +0200 [thread overview]
Message-ID: <YP6qMWbhZKFO9ADf@8bytes.org> (raw)
In-Reply-To: <20210723010552.50969-1-ezequiel@collabora.com>
On Thu, Jul 22, 2021 at 10:05:52PM -0300, Ezequiel Garcia wrote:
> drivers/iommu/dma-iommu.c | 1 +
> 1 file changed, 1 insertion(+)
Applied to iommu/fixes, thanks.
_______________________________________________
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: Ezequiel Garcia <ezequiel@collabora.com>
Cc: iommu@lists.linux-foundation.org, linux-media@vger.kernel.org,
Will Deacon <will@kernel.org>, Christoph Hellwig <hch@lst.de>,
Tomasz Figa <tfiga@chromium.org>,
Ricardo Ribalda <ribalda@chromium.org>,
kernel@collabora.com, stable@vger.kernel.org
Subject: Re: [PATCH] iommu/dma: Fix leak in non-contiguous API
Date: Mon, 26 Jul 2021 14:27:29 +0200 [thread overview]
Message-ID: <YP6qMWbhZKFO9ADf@8bytes.org> (raw)
In-Reply-To: <20210723010552.50969-1-ezequiel@collabora.com>
On Thu, Jul 22, 2021 at 10:05:52PM -0300, Ezequiel Garcia wrote:
> drivers/iommu/dma-iommu.c | 1 +
> 1 file changed, 1 insertion(+)
Applied to iommu/fixes, thanks.
next prev parent reply other threads:[~2021-07-26 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 1:05 [PATCH] iommu/dma: Fix leak in non-contiguous API Ezequiel Garcia
2021-07-23 1:05 ` Ezequiel Garcia
2021-07-23 5:09 ` Christoph Hellwig
2021-07-23 5:09 ` Christoph Hellwig
2021-07-26 12:27 ` Joerg Roedel [this message]
2021-07-26 12:27 ` 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=YP6qMWbhZKFO9ADf@8bytes.org \
--to=joro@8bytes.org \
--cc=ezequiel@collabora.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=kernel@collabora.com \
--cc=linux-media@vger.kernel.org \
--cc=ribalda@chromium.org \
--cc=stable@vger.kernel.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.