From: Harsh Jain <harsh@chelsio.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>,
Atul Gupta <atul.gupta@chelsio.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the crypto tree
Date: Wed, 26 Dec 2018 15:18:17 +0530 [thread overview]
Message-ID: <3bb5d08e-27c3-a088-6584-6f42e241c1a1@chelsio.com> (raw)
In-Reply-To: <20181223123011.qxwfkoib6zadd2rn@gondor.apana.org.au>
On 23-12-2018 18:00, Herbert Xu wrote:
> On Sun, Dec 23, 2018 at 11:13:04PM +1100, Stephen Rothwell wrote:
>> Hi Herbert,
>>
>> Commit
>>
>> 6501ab5ed4d9 ("crypto: chelsio - Reset counters on cxgb4 Detach")
>>
>> is missing a Signed-off-by from its author.
> Hi Stephen:
>
> I believe the issue here is not a missing sign-off from the author,
> but rather that the author was incorrectly set to Harsh who sent
> the email rather than Atul.
>
> Harsh, please add a From header to the patch description in future
> so that the Author field is set correctly.
oops, Will take care next time. Thanks.
>
> Cheers,
next prev parent reply other threads:[~2018-12-26 9:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 12:13 linux-next: Signed-off-by missing for commit in the crypto tree Stephen Rothwell
2018-12-23 12:30 ` Herbert Xu
2018-12-26 9:48 ` Harsh Jain [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
2019-07-27 5:07 Stephen Rothwell
2019-07-27 11:10 ` Herbert Xu
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=3bb5d08e-27c3-a088-6584-6f42e241c1a1@chelsio.com \
--to=harsh@chelsio.com \
--cc=atul.gupta@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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