From: Matthias Brugger <matthias.bgg@gmail.com>
To: Weiyi Lu <weiyi.lu@mediatek.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-clk@vger.kernel.org, srv_heupstream@mediatek.com,
stable@vger.kernel.org, Owen Chen <owen.chen@mediatek.com>
Subject: Re: [PATCH] clk: mediatek: fix mtk_clk_register_mux() as static function
Date: Tue, 10 Nov 2020 11:50:07 +0100 [thread overview]
Message-ID: <00a5aabb-b478-66e0-0663-3cf5557e861b@gmail.com> (raw)
In-Reply-To: <1604972321.16474.9.camel@mtksdaap41>
On 10/11/2020 02:38, Weiyi Lu wrote:
> On Mon, 2020-11-09 at 11:20 +0100, Greg KH wrote:
>> On Mon, Nov 09, 2020 at 05:37:07PM +0800, Weiyi Lu wrote:
>>> mtk_clk_register_mux() should be a static function
>>>
>>> Fixes: a3ae549917f16 ("clk: mediatek: Add new clkmux register API")
>>> Cc: <stable@vger.kernel.org>
>>
>> Why is this for stable trees?
>
> Hi Greg,
>
> My Mistake. Indeed, this is not a bug fix for stable tree.
> And there are simple questions.
> Will I be allowed to keep the fixes tag in this patch to indicate the
> mistakes we made in previous commit if it's not a bug fix for stable
> tree?
> And all I need to do now is to remove stable tree from cc list. Is it
> correct?
That's my understanding, yes. Keep fixes tag but delete cc to stable.
Regards,
Matthias
prev parent reply other threads:[~2020-11-10 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 9:37 [PATCH] clk: mediatek: fix mtk_clk_register_mux() as static function Weiyi Lu
2020-11-09 10:20 ` Greg KH
2020-11-10 1:38 ` Weiyi Lu
2020-11-10 10:50 ` 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=00a5aabb-b478-66e0-0663-3cf5557e861b@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=gregkh@linuxfoundation.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=owen.chen@mediatek.com \
--cc=sboyd@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=stable@vger.kernel.org \
--cc=weiyi.lu@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