From: Tejun Heo <tj@kernel.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
kbuild-all@01.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] phy: brcm-sata: fix semicolon.cocci warnings
Date: Wed, 17 Jan 2018 12:10:47 -0800 [thread overview]
Message-ID: <20180117201047.GX3460072@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180117175118.GA47078@lkp-g5>
On Thu, Jan 18, 2018 at 01:51:18AM +0800, kbuild test robot wrote:
> From: Fengguang Wu <fengguang.wu@intel.com>
>
> drivers/phy/broadcom/phy-brcm-sata.c:534:2-3: Unneeded semicolon
>
>
> Remove unneeded semicolon.
>
> Generated by: scripts/coccinelle/misc/semicolon.cocci
>
> Fixes: 3e507769d15e ("phy: brcm-sata: Implement calibrate callback")
> CC: Florian Fainelli <f.fainelli@gmail.com>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Applied to libata/for-4.16.
Thanks.
--
tejun
prev parent reply other threads:[~2018-01-17 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:51 [tj-libata:for-4.16 14/15] drivers/phy/broadcom/phy-brcm-sata.c:534:2-3: Unneeded semicolon kbuild test robot
2018-01-17 17:51 ` [PATCH] phy: brcm-sata: fix semicolon.cocci warnings kbuild test robot
2018-01-17 20:10 ` Tejun Heo [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=20180117201047.GX3460072@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox