From: Weiyi Lu <weiyi.lu@mediatek.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
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 09:38:41 +0800 [thread overview]
Message-ID: <1604972321.16474.9.camel@mtksdaap41> (raw)
In-Reply-To: <20201109102035.GA1238638@kroah.com>
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?
Many thanks.
>
WARNING: multiple messages have this Message-ID (diff)
From: Weiyi Lu <weiyi.lu@mediatek.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: srv_heupstream@mediatek.com, Stephen Boyd <sboyd@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Owen Chen <owen.chen@mediatek.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: mediatek: fix mtk_clk_register_mux() as static function
Date: Tue, 10 Nov 2020 09:38:41 +0800 [thread overview]
Message-ID: <1604972321.16474.9.camel@mtksdaap41> (raw)
In-Reply-To: <20201109102035.GA1238638@kroah.com>
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?
Many thanks.
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Weiyi Lu <weiyi.lu@mediatek.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: srv_heupstream@mediatek.com, Stephen Boyd <sboyd@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Owen Chen <owen.chen@mediatek.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: mediatek: fix mtk_clk_register_mux() as static function
Date: Tue, 10 Nov 2020 09:38:41 +0800 [thread overview]
Message-ID: <1604972321.16474.9.camel@mtksdaap41> (raw)
In-Reply-To: <20201109102035.GA1238638@kroah.com>
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?
Many thanks.
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-10 1:38 UTC|newest]
Thread overview: 12+ 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 9:37 ` Weiyi Lu
2020-11-09 9:37 ` Weiyi Lu
2020-11-09 10:20 ` Greg KH
2020-11-09 10:20 ` Greg KH
2020-11-09 10:20 ` Greg KH
2020-11-10 1:38 ` Weiyi Lu [this message]
2020-11-10 1:38 ` Weiyi Lu
2020-11-10 1:38 ` Weiyi Lu
2020-11-10 10:50 ` Matthias Brugger
2020-11-10 10:50 ` Matthias Brugger
2020-11-10 10:50 ` Matthias Brugger
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=1604972321.16474.9.camel@mtksdaap41 \
--to=weiyi.lu@mediatek.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=matthias.bgg@gmail.com \
--cc=owen.chen@mediatek.com \
--cc=sboyd@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.