public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Yang Li <yang.lee@linux.alibaba.com>,
	arkadiusz.kubalewski@intel.com, jiri@resnulli.us
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH net-next] netdev: Remove unneeded semicolon
Date: Wed, 20 Sep 2023 12:10:47 +0100	[thread overview]
Message-ID: <0ae9f426-7225-ac4b-4ecd-d53e36dbf365@linux.dev> (raw)
In-Reply-To: <20230919010305.120991-1-yang.lee@linux.alibaba.com>

On 19/09/2023 02:03, Yang Li wrote:
> ./drivers/dpll/dpll_netlink.c:847:3-4: Unneeded semicolon
> 
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=6605
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>

Hi Yang!
There was a report from Intel's bot too about the issue, could you 
please add the tags from it?

Reported-by: kernel test robot <lkp@intel.com>
Closes: 
https://lore.kernel.org/oe-kbuild-all/202309190540.RFwfIgO7-lkp@intel.com/

Thanks!

> ---
>   drivers/dpll/dpll_netlink.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/dpll/dpll_netlink.c b/drivers/dpll/dpll_netlink.c
> index 764437a0661b..e20daba6896a 100644
> --- a/drivers/dpll/dpll_netlink.c
> +++ b/drivers/dpll/dpll_netlink.c
> @@ -844,7 +844,7 @@ dpll_pin_find(u64 clock_id, struct nlattr *mod_name_attr,
>   				return ERR_PTR(-EINVAL);
>   			}
>   			pin_match = pin;
> -		};
> +		}
>   	}
>   	if (!pin_match) {
>   		NL_SET_ERR_MSG(extack, "not found");


  reply	other threads:[~2023-09-20 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  1:03 [PATCH net-next] netdev: Remove unneeded semicolon Yang Li
2023-09-20 11:10 ` Vadim Fedorenko [this message]
2023-09-21 13:07   ` Paolo Abeni
2023-09-21 14:41     ` Vadim Fedorenko
2023-09-21 13:30 ` patchwork-bot+netdevbpf

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=0ae9f426-7225-ac4b-4ecd-d53e36dbf365@linux.dev \
    --to=vadim.fedorenko@linux.dev \
    --cc=abaci@linux.alibaba.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=jiri@resnulli.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yang.lee@linux.alibaba.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