From: Lars Persson <lars.persson@axis•com>
To: Herbert Xu <herbert@gondor•apana.org.au>,
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>,
Rabin Vincent <rabinv@axis•com>, Lars Persson <larper@axis•com>
Subject: Re: linux-next: Signed-off-by missing for commit in the crypto tree
Date: Fri, 4 Aug 2017 11:48:55 +0200 [thread overview]
Message-ID: <357d39d7-a33c-d5e1-31f6-456fba191482@axis.com> (raw)
In-Reply-To: <20170804012955.GA15200@gondor.apana.org.au>
On 08/04/2017 03:29 AM, Herbert Xu wrote:
> On Fri, Aug 04, 2017 at 07:50:22AM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> Commit
>>
>> 9577212cc0e2 ("crypto: hash - add crypto_(un)register_ahashes()")
>>
>> is missing a Signed-off-by from its author.
>
> OK, I've backed out the patches in question. Please resubmit
> with a sign-off. Thanks!
>
Sorry for missing this. We fixed it in patch set v3.
BR,
Lars Persson
next prev parent reply other threads:[~2017-08-04 9:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 21:50 linux-next: Signed-off-by missing for commit in the crypto tree Stephen Rothwell
2017-08-04 1:29 ` Herbert Xu
2017-08-04 9:48 ` Lars Persson [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-23 12:13 Stephen Rothwell
2018-12-23 12:30 ` Herbert Xu
2018-12-26 9:48 ` Harsh Jain
2019-07-27 5:07 Stephen Rothwell
2019-07-27 11:10 ` Herbert Xu
2020-01-09 9:00 Stephen Rothwell
2020-11-13 7:22 Stephen Rothwell
2023-03-13 21:42 Stephen Rothwell
2023-07-16 21:55 Stephen Rothwell
2023-07-17 13:00 ` Mahmoud Adam
2024-10-27 21:15 Stephen Rothwell
2025-05-05 9:55 Stephen Rothwell
2025-05-05 10:22 ` Herbert Xu
2025-05-20 12:45 Stephen Rothwell
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=357d39d7-a33c-d5e1-31f6-456fba191482@axis.com \
--to=lars.persson@axis$(echo .)com \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=larper@axis$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rabinv@axis$(echo .)com \
--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