public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor•apana.org.au>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	"Hook, Gary" <Gary.Hook@amd•com>
Subject: Re: linux-next: Signed-off-by missing for commit in the crypto tree
Date: Sat, 27 Jul 2019 21:10:05 +1000	[thread overview]
Message-ID: <20190727111004.GA17611@gondor.apana.org.au> (raw)
In-Reply-To: <20190727150738.3640330a@canb.auug.org.au>

On Sat, Jul 27, 2019 at 03:07:38PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Commit
> 
>   53a5d5192803 ("crypto: ccp - Log an error message when ccp-crypto fails to load")
> 
> is missing a Signed-off-by from its author.

Thanks Stephen.

Gary, I've backed this patch out.  Please resubmit with a sign-off.

Cheers,
-- 
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

  reply	other threads:[~2019-07-27 11:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27  5:07 linux-next: Signed-off-by missing for commit in the crypto tree Stephen Rothwell
2019-07-27 11:10 ` Herbert Xu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-20 12:45 Stephen Rothwell
2025-05-05  9:55 Stephen Rothwell
2025-05-05 10:22 ` Herbert Xu
2024-10-27 21:15 Stephen Rothwell
2023-07-16 21:55 Stephen Rothwell
2023-07-17 13:00 ` Mahmoud Adam
2023-03-13 21:42 Stephen Rothwell
2020-11-13  7:22 Stephen Rothwell
2020-01-09  9:00 Stephen Rothwell
2018-12-23 12:13 Stephen Rothwell
2018-12-23 12:30 ` Herbert Xu
2018-12-26  9:48   ` Harsh Jain
2017-08-03 21:50 Stephen Rothwell
2017-08-04  1:29 ` Herbert Xu
2017-08-04  9:48   ` Lars Persson

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=20190727111004.GA17611@gondor.apana.org.au \
    --to=herbert@gondor$(echo .)apana.org.au \
    --cc=Gary.Hook@amd$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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