From: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Mark Brown <broonie@kernel.org>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>, Yong Wu <yong.wu@mediatek.com>,
kernelci-results@groups.io, bot@kernelci.org
Cc: gtucker@collabora.com, iommu@lists.linux.dev,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, mingyuan.ma@mediatek.com,
libo.kang@mediatek.com, chengci.xu@mediatek.com,
yf.wang@mediatek.com, youlin.pei@mediatek.com,
anan.sun@mediatek.com, xueqi.zhang@mediatek.com,
Guenter Roeck <groeck@chromium.org>
Subject: Re: next/master bisection: baseline.login on mt8173-elm-hana
Date: Fri, 16 Dec 2022 13:21:10 +0100 [thread overview]
Message-ID: <1614dc0c-dadf-a092-05d4-bdec1b2c2ae9@gmail.com> (raw)
In-Reply-To: <64296af0-e2b9-6f39-7dbc-6e0120f96fe2@collabora.com>
On 16/12/2022 12:44, AngeloGioacchino Del Regno wrote:
> Il 16/12/22 12:42, Matthias Brugger ha scritto:
>> Yong, Angelo, can you have a look?
>>
>> If not I'd propose to drop the series for now until we understand what is
>> going wrong.
>>
>> Regards,
>> Matthias
>>
>
> It's fixed already, and picked upstream [1]... that was happening on more than
> just MT8173! :-)
>
> [1]:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/iommu/mtk_iommu.c?h=next-20221216&id=462e768b55a2331324ff72e74706261134369826
>
Ah saw that patch today and marked to look into it later. Perfect, one thing
less to care about :)
prev parent reply other threads:[~2022-12-16 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6391e1c4.170a0220.b562d.3c9c@mx.google.com>
2022-12-08 13:48 ` next/master bisection: baseline.login on mt8173-elm-hana Mark Brown
2022-12-16 11:42 ` Matthias Brugger
2022-12-16 11:44 ` AngeloGioacchino Del Regno
2022-12-16 12:21 ` Matthias Brugger [this message]
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=1614dc0c-dadf-a092-05d4-bdec1b2c2ae9@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=anan.sun@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=chengci.xu@mediatek.com \
--cc=groeck@chromium.org \
--cc=gtucker@collabora.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kernelci-results@groups.io \
--cc=libo.kang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mingyuan.ma@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox