public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Wolfgang Grandegger <wg@grandegger.com>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-can@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] can: mcp251xfd: fix semicolon.cocci warnings
Date: Mon, 19 Oct 2020 20:11:16 +0200	[thread overview]
Message-ID: <87d0ad42-e32b-766c-ad73-0d75e7a241f8@pengutronix.de> (raw)
In-Reply-To: <20201019120805.GA63693@ae4257e0ab22>


[-- Attachment #1.1: Type: text/plain, Size: 839 bytes --]

On 10/19/20 2:08 PM, kernel test robot wrote:
> From: kernel test robot <lkp@intel.com>
> 
> drivers/net/can/spi/mcp251xfd/mcp251xfd-regmap.c:176:2-3: Unneeded semicolon
> 
> 
>  Remove unneeded semicolon.
> 
> Generated by: scripts/coccinelle/misc/semicolon.cocci
> 
> Fixes: f4f77366f21d ("can: mcp251xfd: rename all user facing strings to mcp251xfd")

The correct fixes tag is:

Fixes: 875347fe5756 ("can: mcp25xxfd: add regmap infrastructure")

> Signed-off-by: kernel test robot <lkp@intel.com>

Applied with that to linux-can.

tnx,
Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-10-20  6:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202010192040.u25q5Ddd-lkp@intel.com>
2020-10-19 12:08 ` [PATCH] can: mcp251xfd: fix semicolon.cocci warnings kernel test robot
2020-10-19 18:11   ` Marc Kleine-Budde [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=87d0ad42-e32b-766c-ad73-0d75e7a241f8@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=kbuild-all@lists.01.org \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=wg@grandegger.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