From: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Owen Chen <owen.chen@mediatek.com>,
Mars Cheng <mars.cheng@mediatek.com>,
Macpaul Lin <macpaul.lin@mediatek.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: mediatek: Remove unused configs with COMMON_CLK_MT6765 prefix
Date: Tue, 28 Mar 2023 17:45:02 +0200 [thread overview]
Message-ID: <78a6478d-b8c3-e46f-e995-c4813b6e76f7@gmail.com> (raw)
In-Reply-To: <98c0a46d-05da-7863-1a30-51727c20da23@collabora.com>
On 3/21/23 09:55, AngeloGioacchino Del Regno wrote:
> Il 21/03/23 05:26, Lukas Bulwahn ha scritto:
>> Commit 1aca9939bf72 ("clk: mediatek: Add MT6765 clock support") adds
>> fourteen configs with COMMON_CLK_MT6765 prefix, but only uses seven of
>> them
>> to configure inclusion of drivers.
>>
>> Remove the seven unused COMMON_CLK_MT6765 configs.
>>
>> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>
> Please add the required Fixes tag (you even reference the commit to fix
> already!),
> then you'll get my R-b at v2 :-)
>
What bug get's fixed by this? This is just a code clean-up, no bug get's
fixed with it. So there is no reason to be backported to any stable or
distribution kernels.
Regards,
Matthias
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-28 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 4:26 [PATCH] clk: mediatek: Remove unused configs with COMMON_CLK_MT6765 prefix Lukas Bulwahn
2023-03-21 8:55 ` AngeloGioacchino Del Regno
2023-03-28 15:45 ` 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=78a6478d-b8c3-e46f-e995-c4813b6e76f7@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lukas.bulwahn@gmail.com \
--cc=macpaul.lin@mediatek.com \
--cc=mars.cheng@mediatek.com \
--cc=mturquette@baylibre.com \
--cc=owen.chen@mediatek.com \
--cc=sboyd@kernel.org \
/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).