From: Guodong Liu <guodong.liu@mediatek.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "kernel test robot" <lkp@intel.com>,
kbuild-all@lists.01.org, linux-gpio@vger.kernel.org,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Subject: Re: [linusw-pinctrl:devel 17/19] drivers/pinctrl/mediatek/pinctrl-mt8192.c:1362:56: warning: "/*" within comment
Date: Mon, 27 Jun 2022 17:39:48 +0800 [thread overview]
Message-ID: <01de866e45dc3a93926dd1348c95f6dbe342ed3b.camel@mediatek.com> (raw)
In-Reply-To: <CACRpkdauOS31Yof2p9XaGBc4amKYqjNyhGX1zF=Sgc5D7ozT3w@mail.gmail.com>
-----Original Message-----
From: Linus Walleij <linus.walleij@linaro.org>
To: Guodong Liu <guodong.liu@mediatek.com>
Cc: kernel test robot <lkp@intel.com>, kbuild-all@lists.01.org,
linux-gpio@vger.kernel.org, Nícolas F. R. A. Prado <
nfraprado@collabora.com>
Subject: Re: [linusw-pinctrl:devel 17/19]
drivers/pinctrl/mediatek/pinctrl-mt8192.c:1362:56: warning: "/*" within
comment
Date: Mon, 27 Jun 2022 09:53:54 +0200
On Mon, Jun 27, 2022 at 4:02 AM Guodong Liu <guodong.liu@mediatek.com>
wrote:
> I don't know which patch you mean, I just wrote a patch to fix it
> so my tree builds cleanly, thanks!
> evolution
>
> Fixed in Bellow patch, thanks!
>
>
https://patchwork.kernel.org/project/linux-mediatek/patch/20220626043955.32756-4-guodong.liu@mediatek.com/
It's better to fix it in a separate patch so I used mine, please
rebase this series on the
devel branch.
Thanks for you kindly help to fixed in commit "28d860dd08d5" !
Yours,
Linus Walleij
prev parent reply other threads:[~2022-06-27 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 1:04 [linusw-pinctrl:devel 17/19] drivers/pinctrl/mediatek/pinctrl-mt8192.c:1362:56: warning: "/*" within comment kernel test robot
2022-06-26 4:48 ` Guodong Liu
2022-06-27 0:03 ` Linus Walleij
2022-06-27 2:01 ` Guodong Liu
2022-06-27 7:53 ` Linus Walleij
2022-06-27 9:39 ` Guodong Liu [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=01de866e45dc3a93926dd1348c95f6dbe342ed3b.camel@mediatek.com \
--to=guodong.liu@mediatek.com \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nfraprado@collabora.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).