All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Llamas <cmllamas@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	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 mm-stable tree
Date: Thu, 13 Oct 2022 04:43:13 +0000	[thread overview]
Message-ID: <Y0eXYYG4FXbdNbYO@google.com> (raw)
In-Reply-To: <20221013104234.11e88852@canb.auug.org.au>

On Thu, Oct 13, 2022 at 10:42:34AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Commit
> 
>   db24ef4e6b0a ("mm/mmap: undo ->mmap() when arch_validate_flags() fails")
> 
> is missing a Signed-off-by from its author.
> 
> -- 
> Cheers,
> Stephen Rothwell

Sorry this was my fault as I used a three-dash line to comment a code
section in the commit message. Which instead just cuts the commit log
short when applying the patch. Sigh.

You can see this in the original post:
https://lkml.kernel.org/r/20220930003844.1210987-1-cmllamas@google.com

I believe Andrew noticed this error and fixed the patch. However, the
Signed-off-by tag probably got dropped in the process. I'm unsure if
this can be amended in the mm tree?

Thanks Stephen for flagging this and apologies Andrew for the trouble.

--
Carlos Llamas

  reply	other threads:[~2022-10-13  4:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 23:42 linux-next: Signed-off-by missing for commit in the mm-stable tree Stephen Rothwell
2022-10-13  4:43 ` Carlos Llamas [this message]
2022-10-13 12:41   ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2022-06-27 22:00 Stephen Rothwell
2022-05-13  7:05 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=Y0eXYYG4FXbdNbYO@google.com \
    --to=cmllamas@google.com \
    --cc=akpm@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.