From: Hanks Chen <hanks.chen@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
YueHaibing <yuehaibing@huawei.com>,
mtk01761 <wendell.lin@mediatek.com>,
CC Hwang <cc.hwang@mediatek.com>, <linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <wsd_upstream@mediatek.com>
Subject: Re: [PATCH v2 0/2] Remove MT6779 UART3 clock support
Date: Thu, 30 Jul 2020 21:04:32 +0800 [thread overview]
Message-ID: <1596114272.18804.1.camel@mtkswgap22> (raw)
In-Reply-To: <252ba954-ae8f-18a3-55a3-9dd844a4d5b6@gmail.com>
Hi all,
Gentle ping on this patch.
Thanks!
Hanks Chen
On Wed, 2020-07-22 at 17:21 +0200, Matthias Brugger wrote:
>
> On 22/07/2020 13:16, Hanks Chen wrote:
> > On Wed, 2020-07-22 at 10:43 +0200, Matthias Brugger wrote:
> >>
> >> On 22/07/2020 05:09, Hanks Chen wrote:
> >>> remove the redundant clk interface of uart.
> >>> CLK_INFRA_UART3 is a dummy clk interface,
> >>> it has no effect on the operation of the read/write instruction.
> >>>
> >>> Change since v2:
> >>> Commit "dt-bindings: clock: remove UART3 clock support"
> >>
> >> Sorry just another comment. I think we can make this one patch deleting everything.
> >>
> > Sorry, I don't understand the comment. Do I need to merge them into one
> > big patch?
> > Btw, if I use one patch, I would get check patch fail.
> > ---
> > [2020-07-22 19:12:49,046 ERROR] Run check patch results:
> > WARNING:DT_SPLIT_BINDING_PATCH: DT binding docs and includes should be a
> > separate patch. See:
> > Documentation/devicetree/bindings/submitting-patches.rst
> > ---
>
> Hm, I think that's a debatable error message from checkpatch, but let's leave it
> as it is.
>
> Regards,
> Matthias
>
>
> >
> > Hanks
> >
> >>> -- remove Fixes tag
> >>> Commit "clk: mediatek: remove UART3 clock support"
> >>> -- remove Fixes tag
> >>>
> >>> Hanks Chen (2):
> >>> dt-bindings: clock: remove UART3 clock support
> >>> clk: mediatek: remove UART3 clock support
> >>>
> >>> drivers/clk/mediatek/clk-mt6779.c | 2 --
> >>> include/dt-bindings/clock/mt6779-clk.h | 1 -
> >>> 2 files changed, 3 deletions(-)
> >>>
> >
next prev parent reply other threads:[~2020-07-30 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 3:09 [PATCH v2 0/2] Remove MT6779 UART3 clock support Hanks Chen
2020-07-22 3:09 ` [PATCH v2 1/2] dt-bindings: clock: remove " Hanks Chen
2020-07-22 15:22 ` Matthias Brugger
2020-07-22 3:09 ` [PATCH v2 2/2] clk: mediatek: " Hanks Chen
2020-07-22 15:22 ` Matthias Brugger
2020-07-22 8:43 ` [PATCH v2 0/2] Remove MT6779 " Matthias Brugger
2020-07-22 11:16 ` Hanks Chen
2020-07-22 15:21 ` Matthias Brugger
2020-07-30 13:04 ` Hanks Chen [this message]
2020-09-08 6:31 ` Hanks Chen
2020-09-25 12:43 ` Hanks Chen
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=1596114272.18804.1.camel@mtkswgap22 \
--to=hanks.chen@mediatek.com \
--cc=cc.hwang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=wendell.lin@mediatek.com \
--cc=wsd_upstream@mediatek.com \
--cc=yuehaibing@huawei.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).