From: Parav Pandit <parav@nvidia.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
Saeed Mahameed <saeedm@nvidia.com>
Cc: "leon@kernel.org" <leon@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] net/mlx5: remove unneeded semicolon
Date: Mon, 22 Feb 2021 10:01:54 +0000 [thread overview]
Message-ID: <BY5PR12MB4322C25D61EC6E4549370917DC819@BY5PR12MB4322.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1613987819-43161-1-git-send-email-jiapeng.chong@linux.alibaba.com>
> From: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> Sent: Monday, February 22, 2021 3:27 PM
>
> Fix the following coccicheck warnings:
>
> ./drivers/net/ethernet/mellanox/mlx5/core/sf/devlink.c:495:2-3: Unneeded
> semicolon.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> drivers/net/ethernet/mellanox/mlx5/core/sf/devlink.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/sf/devlink.c
> b/drivers/net/ethernet/mellanox/mlx5/core/sf/devlink.c
> index c2ba41b..60a6328 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/sf/devlink.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/sf/devlink.c
> @@ -492,7 +492,7 @@ static int mlx5_sf_esw_event(struct notifier_block
> *nb, unsigned long event, voi
> break;
> default:
> break;
> - };
> + }
>
> return 0;
> }
> --
> 1.8.3.1
Reviewed-by: Parav Pandit <parav@nvidia.com>
next prev parent reply other threads:[~2021-02-22 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 9:56 [PATCH] net/mlx5: remove unneeded semicolon Jiapeng Chong
2021-02-22 10:01 ` Parav Pandit [this message]
2021-03-03 8:52 ` Parav Pandit
2021-03-11 23:24 ` Saeed Mahameed
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=BY5PR12MB4322C25D61EC6E4549370917DC819@BY5PR12MB4322.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=davem@davemloft.net \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.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).