linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Li <ashimida@linux.alibaba.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the kbuild-current tree
Date: Sun, 23 Oct 2022 23:34:15 -0700	[thread overview]
Message-ID: <a49605d6-6e1f-78c8-9774-423891089052@linux.alibaba.com> (raw)
In-Reply-To: <20221023124810.51b1201b@canb.auug.org.au>



On 10/22/22 18:48, Stephen Rothwell wrote:
> Hi all,
> 
> Commit
> 
>    9a21115ca50e ("Documentation: kbuild: Add description of git for reproducible builds")
> 
> is missing a Signed-off-by from its committer.
> 
> Also, I am guessing (I haven't actually done the build, yet) that this
> will produce a new build warning from (e.g.) "make htmldocs", as the
> underlining of the new "Git" header line is longer than it should be.

Oh yes, I didn't see a warning when compiling, but it should be aligned
here, sorry for the typo.

To Masahiro:
Do I need to submit a V2 to remove the extra underscore here? I'm willing
to if needed :)

Thanks, Dan.

> 

  reply	other threads:[~2022-10-24  6:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23  1:48 linux-next: Signed-off-by missing for commit in the kbuild-current tree Stephen Rothwell
2022-10-24  6:34 ` Dan Li [this message]
2022-10-27 15:02   ` Masahiro Yamada
  -- strict thread matches above, loose matches on Subject: below --
2022-08-18  4:46 Stephen Rothwell
2019-10-07 20:05 Stephen Rothwell
2019-10-08  2:37 ` Masahiro Yamada

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=a49605d6-6e1f-78c8-9774-423891089052@linux.alibaba.com \
    --to=ashimida@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=masahiroy@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;
as well as URLs for NNTP newsgroup(s).