All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: yf.wang@mediatek.com
Cc: Robin Murphy <robin.murphy@arm.com>,
	Will Deacon <will@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	"open list:IOMMU DMA-API LAYER" <iommu@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-arm-kernel@lists.infradead.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>,
	wsd_upstream@mediatek.com, stable@vger.kernel.org,
	Libo Kang <Libo.Kang@mediatek.com>,
	Yong Wu <yong.wu@mediatek.com>, Ning Li <Ning.Li@mediatek.com>,
	jianjiao zeng <jianjiao.zeng@mediatek.com>
Subject: Re: [PATCH v2] iommu/iova: Fix alloc iova overflows issue
Date: Fri, 13 Jan 2023 13:43:25 +0100	[thread overview]
Message-ID: <Y8FR7U8YaDrIF62d@8bytes.org> (raw)
In-Reply-To: <20230111063801.25107-1-yf.wang@mediatek.com>

On Wed, Jan 11, 2023 at 02:38:00PM +0800, yf.wang@mediatek.com wrote:
> v2: Update patch
>     1. Cc stable@vger.kernel.org
>        This patch needs to be merged stable branch,
>        add stable@vger.kernel.org in mail list.
>     2. Refer robin's suggestion to update patch.

Applied for 6.2, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: yf.wang@mediatek.com
Cc: Robin Murphy <robin.murphy@arm.com>,
	Will Deacon <will@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	"open list:IOMMU DMA-API LAYER" <iommu@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-arm-kernel@lists.infradead.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>,
	wsd_upstream@mediatek.com, stable@vger.kernel.org,
	Libo Kang <Libo.Kang@mediatek.com>,
	Yong Wu <yong.wu@mediatek.com>, Ning Li <Ning.Li@mediatek.com>,
	jianjiao zeng <jianjiao.zeng@mediatek.com>
Subject: Re: [PATCH v2] iommu/iova: Fix alloc iova overflows issue
Date: Fri, 13 Jan 2023 13:43:25 +0100	[thread overview]
Message-ID: <Y8FR7U8YaDrIF62d@8bytes.org> (raw)
In-Reply-To: <20230111063801.25107-1-yf.wang@mediatek.com>

On Wed, Jan 11, 2023 at 02:38:00PM +0800, yf.wang@mediatek.com wrote:
> v2: Update patch
>     1. Cc stable@vger.kernel.org
>        This patch needs to be merged stable branch,
>        add stable@vger.kernel.org in mail list.
>     2. Refer robin's suggestion to update patch.

Applied for 6.2, thanks.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-01-13 12:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11  6:38 [PATCH v2] iommu/iova: Fix alloc iova overflows issue yf.wang
2023-01-11  6:38 ` yf.wang
2023-01-11 12:11 ` Robin Murphy
2023-01-11 12:11   ` Robin Murphy
2023-01-13 12:43 ` Joerg Roedel [this message]
2023-01-13 12:43   ` 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=Y8FR7U8YaDrIF62d@8bytes.org \
    --to=joro@8bytes.org \
    --cc=Libo.Kang@mediatek.com \
    --cc=Ning.Li@mediatek.com \
    --cc=iommu@lists.linux.dev \
    --cc=jianjiao.zeng@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=stable@vger.kernel.org \
    --cc=will@kernel.org \
    --cc=wsd_upstream@mediatek.com \
    --cc=yf.wang@mediatek.com \
    --cc=yong.wu@mediatek.com \
    /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.