[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220511084222.GO4031@kadam>
Date: Wed, 11 May 2022 11:42:22 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Yong Wu <yong.wu@...iatek.com>
Cc: Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
iommu@...ts.linux-foundation.org,
linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
mingyuan.ma@...iatek.com, yf.wang@...iatek.com,
libo.kang@...iatek.com, chengci.xu@...iatek.com,
youlin.pei@...iatek.com, anan.sun@...iatek.com,
xueqi.zhang@...iatek.com, Guenter Roeck <groeck@...omium.org>
Subject: Re: [PATCH 1/4] iommu/mediatek: Use dev_err_probe to mute
probe_defer err log
On Wed, May 11, 2022 at 02:49:17PM +0800, Yong Wu wrote:
> Fixes: d2e9a1102cfc ("iommu/mediatek: Contain MM IOMMU flow with the MM TYPE")
> Signed-off-by: Yong Wu <yong.wu@...iatek.com>
> ---
> The Fixes tag commit-id is from linux-next.
This is fine. The commit hash will not change unless the maintainer
rebases the tree.
When maintainers rebase their trees it's their responsibility to deal
with the Fixes tags. Often they just fold the fix into the original
commit so the issue is moot. Stephen Rothwell checks that Fixes tags
point to a valid commit and there are probably other people who have
checks for that as well.
regards,
dan carpenter
Powered by blists - more mailing lists