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 [thread overview]
Message-ID: <CACRpkdauOS31Yof2p9XaGBc4amKYqjNyhGX1zF=Sgc5D7ozT3w@mail.gmail.com> (raw)
In-Reply-To: <208aa8069584038593cbcb18f7f049f650782145.camel@mediatek.com>
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.
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: kbuild-all@lists.01.org
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 [thread overview]
Message-ID: <CACRpkdauOS31Yof2p9XaGBc4amKYqjNyhGX1zF=Sgc5D7ozT3w@mail.gmail.com> (raw)
In-Reply-To: <208aa8069584038593cbcb18f7f049f650782145.camel@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
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(a)mediatek.com/
It's better to fix it in a separate patch so I used mine, please
rebase this series on the
devel branch.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-06-27 7:54 UTC|newest]
Thread overview: 11+ 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 3:04 ` Guodong Liu
2022-06-27 0:03 ` Linus Walleij
2022-06-27 0:03 ` Linus Walleij
2022-06-27 2:01 ` Guodong Liu
2022-06-27 2:01 ` Guodong Liu
2022-06-27 7:53 ` Linus Walleij [this message]
2022-06-27 7:53 ` Linus Walleij
2022-06-27 9:39 ` Guodong Liu
2022-06-27 9:39 ` Guodong Liu
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='CACRpkdauOS31Yof2p9XaGBc4amKYqjNyhGX1zF=Sgc5D7ozT3w@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=guodong.liu@mediatek.com \
--cc=kbuild-all@lists.01.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 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.