From: Peter Gonda <pgonda@google.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: kernel test robot <lkp@intel.com>,
David Rientjes <rientjes@google.com>,
kbuild-all@lists.01.org,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Marc Orr <marcorr@google.com>
Subject: Re: [PATCH] crypto: fix semicolon.cocci warnings
Date: Tue, 4 Jan 2022 14:14:16 -0700 [thread overview]
Message-ID: <CAMkAt6rreu0X6DFENqYAAJ_JMEWoS8cvgf7bDhzgFxAnZturrg@mail.gmail.com> (raw)
In-Reply-To: <YcU+ZNqZ+pNv06QL@gondor.apana.org.au>
On Thu, Dec 23, 2021 at 8:28 PM Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> On Sat, Dec 18, 2021 at 09:25:42PM +0800, kernel test robot wrote:
> > From: kernel test robot <lkp@intel.com>
> >
> > drivers/crypto/ccp/sev-dev.c:263:2-3: Unneeded semicolon
> >
> >
> > Remove unneeded semicolon.
> >
> > Generated by: scripts/coccinelle/misc/semicolon.cocci
> >
> > Fixes: 3d725965f836 ("crypto: ccp - Add SEV_INIT_EX support")
> > CC: David Rientjes <rientjes@google.com>
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: kernel test robot <lkp@intel.com>
> > ---
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
> > head: 696645d25bafd6ba3562611c29bc8ecd47066dfe
> > commit: 3d725965f836a7acbd1674e33644bec18373de53 [83/95] crypto: ccp - Add SEV_INIT_EX support
> > :::::: branch date: 31 hours ago
> > :::::: commit date: 31 hours ago
> >
> > sev-dev.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> I don't know what happened but your patch isn't in patchwork.
> Could you please try resending?
Herbert I see the patches I sent here:
https://patchwork.kernel.org/project/linux-crypto/list/?series=591933&state=%2A&archive=both.
Are you asking for this bot to resend? Or should I send a fix up patch
if that's easier.
>
> Thanks,
> --
> Email: Herbert Xu <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2022-01-04 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 13:25 [PATCH] crypto: fix semicolon.cocci warnings kernel test robot
2021-12-24 3:28 ` Herbert Xu
2022-01-04 21:14 ` Peter Gonda [this message]
2022-01-05 0:29 ` Herbert Xu
2022-01-05 15:20 ` Peter Gonda
-- strict thread matches above, loose matches on Subject: below --
2019-11-01 8:52 Julia Lawall
2019-11-01 12:50 ` Corentin Labbe
2019-11-08 15:20 ` Herbert Xu
2019-11-01 8:24 [cryptodev:master 150/163] drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c:558:52-53: Unneeded semicolon kbuild test robot
2019-11-01 8:24 ` [PATCH] crypto: fix semicolon.cocci warnings kbuild test robot
2016-06-15 11:13 [cryptodev:master 47/51] crypto/drbg.c:1637:39-40: Unneeded semicolon kbuild test robot
2016-06-15 11:13 ` [PATCH] crypto: fix semicolon.cocci warnings kbuild test robot
2016-06-15 11:40 ` Stephan Mueller
2016-06-20 11:33 ` Herbert Xu
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=CAMkAt6rreu0X6DFENqYAAJ_JMEWoS8cvgf7bDhzgFxAnZturrg@mail.gmail.com \
--to=pgonda@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@lists.01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=lkp@intel.com \
--cc=marcorr@google.com \
--cc=rientjes@google.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).