[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <00a5aabb-b478-66e0-0663-3cf5557e861b@gmail.com>
Date: Tue, 10 Nov 2020 11:50:07 +0100
From: Matthias Brugger <matthias.bgg@...il.com>
To: Weiyi Lu <weiyi.lu@...iatek.com>,
Greg KH <gregkh@...uxfoundation.org>
Cc: Stephen Boyd <sboyd@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-clk@...r.kernel.org,
srv_heupstream@...iatek.com, stable@...r.kernel.org,
Owen Chen <owen.chen@...iatek.com>
Subject: Re: [PATCH] clk: mediatek: fix mtk_clk_register_mux() as static
function
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@...r.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
Powered by blists - more mailing lists