From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Mark Brown <broonie@kernel.org>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
matthias.bgg@gmail.com, zhiyong.tao@mediatek.com,
colin.king@intel.com, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
wenst@chromium.org
Subject: Re: [PATCH] Revert "serial: 8250_mtk: Make sure to select the right FEATURE_SEL"
Date: Tue, 10 May 2022 14:46:28 +0200 [thread overview]
Message-ID: <b13b019f-f766-60df-3764-d375f64ea7d3@collabora.com> (raw)
In-Reply-To: <YnpeYGbo7JJK0lDk@sirena.org.uk>
Il 10/05/22 14:45, Mark Brown ha scritto:
> On Tue, May 10, 2022 at 02:26:20PM +0200, AngeloGioacchino Del Regno wrote:
>> It was found that some MediaTek SoCs are incompatible with this
>> change. Also, this register was mistakenly understood as it was
>> related to the 16550A register layout selection but, at least
>> on some IPs, if not all, it's related to something else unknown.
>>
>> This reverts commit 6f81fdded0d024c7d4084d434764f30bca1cd6b1.
>>
>> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>> ---
>
> Reported-by: "kernelci.org bot" <bot@kernelci.org>
Sorry for missing this tag, and also I'm sorry for the noise.
Regards,
Angelo
next prev parent reply other threads:[~2022-05-10 12:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 12:26 [PATCH] Revert "serial: 8250_mtk: Make sure to select the right FEATURE_SEL" AngeloGioacchino Del Regno
2022-05-10 12:45 ` Mark Brown
2022-05-10 12:46 ` AngeloGioacchino Del Regno [this message]
2022-05-10 12:56 ` Mark Brown
2022-05-10 15:29 ` AngeloGioacchino Del Regno
2022-05-23 10:17 ` AngeloGioacchino Del Regno
2022-05-23 12:10 ` Greg KH
2022-05-23 12:13 ` AngeloGioacchino Del Regno
2022-05-23 12:32 ` Greg KH
2022-05-23 13:25 ` AngeloGioacchino Del Regno
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=b13b019f-f766-60df-3764-d375f64ea7d3@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=colin.king@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=wenst@chromium.org \
--cc=zhiyong.tao@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;
as well as URLs for NNTP newsgroup(s).