All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Yong Wu <yong.wu@mediatek.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	iommu@lists.linux.dev, linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	mingyuan.ma@mediatek.com, yf.wang@mediatek.com,
	libo.kang@mediatek.com, chengci.xu@mediatek.com,
	youlin.pei@mediatek.com, anan.sun@mediatek.com,
	xueqi.zhang@mediatek.com, Guenter Roeck <groeck@chromium.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v7 0/6] iommu/mediatek: Improve safety from invalid dts input
Date: Mon, 5 Dec 2022 11:46:26 +0100	[thread overview]
Message-ID: <Y43MAvPRx2BrRy/X@8bytes.org> (raw)
In-Reply-To: <20221018024258.19073-1-yong.wu@mediatek.com>

On Tue, Oct 18, 2022 at 10:42:52AM +0800, Yong Wu wrote:
> Guenter Roeck (1):
>   iommu/mediatek: Validate number of phandles associated with
>     "mediatek,larbs"
> 
> Yong Wu (5):
>   iommu/mediatek: Add platform_device_put for recovering the device
>     refcnt
>   iommu/mediatek: Use component_match_add
>   iommu/mediatek: Add error path for loop of mm_dts_parse
>   iommu/mediatek: Improve safety for mediatek,smi property in larb nodes
>   iommu/mediatek: Remove unused "mapping" member from mtk_iommu_data

Applied, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Yong Wu <yong.wu@mediatek.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	iommu@lists.linux.dev, linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	mingyuan.ma@mediatek.com, yf.wang@mediatek.com,
	libo.kang@mediatek.com, chengci.xu@mediatek.com,
	youlin.pei@mediatek.com, anan.sun@mediatek.com,
	xueqi.zhang@mediatek.com, Guenter Roeck <groeck@chromium.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v7 0/6] iommu/mediatek: Improve safety from invalid dts input
Date: Mon, 5 Dec 2022 11:46:26 +0100	[thread overview]
Message-ID: <Y43MAvPRx2BrRy/X@8bytes.org> (raw)
In-Reply-To: <20221018024258.19073-1-yong.wu@mediatek.com>

On Tue, Oct 18, 2022 at 10:42:52AM +0800, Yong Wu wrote:
> Guenter Roeck (1):
>   iommu/mediatek: Validate number of phandles associated with
>     "mediatek,larbs"
> 
> Yong Wu (5):
>   iommu/mediatek: Add platform_device_put for recovering the device
>     refcnt
>   iommu/mediatek: Use component_match_add
>   iommu/mediatek: Add error path for loop of mm_dts_parse
>   iommu/mediatek: Improve safety for mediatek,smi property in larb nodes
>   iommu/mediatek: Remove unused "mapping" member from mtk_iommu_data

Applied, 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:[~2022-12-05 10:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  2:42 [PATCH v7 0/6] iommu/mediatek: Improve safety from invalid dts input Yong Wu
2022-10-18  2:42 ` Yong Wu
2022-10-18  2:42 ` [PATCH v7 1/6] iommu/mediatek: Add platform_device_put for recovering the device refcnt Yong Wu
2022-10-18  2:42   ` Yong Wu
2022-11-22 16:24   ` Matthias Brugger
2022-11-22 16:24     ` Matthias Brugger
2022-10-18  2:42 ` [PATCH v7 2/6] iommu/mediatek: Use component_match_add Yong Wu
2022-10-18  2:42   ` Yong Wu
2022-11-22 16:28   ` Matthias Brugger
2022-11-22 16:28     ` Matthias Brugger
2022-10-18  2:42 ` [PATCH v7 3/6] iommu/mediatek: Add error path for loop of mm_dts_parse Yong Wu
2022-10-18  2:42   ` Yong Wu
2022-11-22 16:32   ` Matthias Brugger
2022-11-22 16:32     ` Matthias Brugger
2022-10-18  2:42 ` [PATCH v7 4/6] iommu/mediatek: Validate number of phandles associated with "mediatek,larbs" Yong Wu
2022-10-18  2:42   ` Yong Wu
2022-11-22 16:43   ` Matthias Brugger
2022-11-22 16:43     ` Matthias Brugger
2022-10-18  2:42 ` [PATCH v7 5/6] iommu/mediatek: Improve safety for mediatek,smi property in larb nodes Yong Wu
2022-10-18  2:42   ` Yong Wu
2022-11-22 16:49   ` Matthias Brugger
2022-11-22 16:49     ` Matthias Brugger
2022-10-18  2:42 ` [PATCH v7 6/6] iommu/mediatek: Remove unused "mapping" member from mtk_iommu_data Yong Wu
2022-10-18  2:42   ` Yong Wu
2022-11-22  1:13 ` [PATCH v7 0/6] iommu/mediatek: Improve safety from invalid dts input Yong Wu (吴勇)
2022-11-22  1:13   ` Yong Wu (吴勇)
2022-11-22  8:30   ` joro
2022-11-22  8:30     ` joro
2022-12-05 10:46 ` Joerg Roedel [this message]
2022-12-05 10:46   ` 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=Y43MAvPRx2BrRy/X@8bytes.org \
    --to=joro@8bytes.org \
    --cc=anan.sun@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chengci.xu@mediatek.com \
    --cc=dan.carpenter@oracle.com \
    --cc=groeck@chromium.org \
    --cc=iommu@lists.linux.dev \
    --cc=libo.kang@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=mingyuan.ma@mediatek.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=xueqi.zhang@mediatek.com \
    --cc=yf.wang@mediatek.com \
    --cc=yong.wu@mediatek.com \
    --cc=youlin.pei@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.