linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fabio.maria.de.francesco@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Fabio De Francesco <fabio.maria.de.francesco@intel.com>,
	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 tree
Date: Wed, 22 Nov 2023 16:20:02 +0100	[thread overview]
Message-ID: <4884533.31r3eYUQgx@fdefranc-mobl3> (raw)
In-Reply-To: <20231121083951.5b314a98@canb.auug.org.au>

On Monday, 20 November 2023 22:39:51 CET Stephen Rothwell wrote:
> Hi all,
>
> Commit
> 
>   b2419063123e ("mm/util: use kmap_local_page() in memcmp_pages()")
> 
> is missing a Signed-off-by from its author.
> 
> Well, not actually, but it helps if the Author of the commit and the
> Signed-off-by use the same email address (or slightly more similar
> than this:
> 
> Author: Fabio De Francesco <fabio.maria.de.francesco@intel.com>
> Signed-off-by: Fabio M. De Francesco
> <fabio.maria.de.francesco@linux.intel.com>

I'm sorry for this mistake. This was the first patch I sent using the 
[*].intel.com domains, so I was expecting that something could have been badly 
configured.

I think that the other four MM patches I sent the same day have no problems.
I'll be more careful next time.

Thanks,

Fabio




  reply	other threads:[~2023-11-22 15:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 21:39 linux-next: Signed-off-by missing for commit in the mm tree Stephen Rothwell
2023-11-22 15:20 ` Fabio M. De Francesco [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-02 20:55 Stephen Rothwell
2023-10-02 22:06 ` Roman Gushchin
2022-12-17 20:59 Stephen Rothwell
2022-11-23 22:13 Stephen Rothwell
2022-11-24  0:16 ` Andrew Morton
2022-09-05 21:59 Stephen Rothwell
2022-06-09  0:44 Stephen Rothwell
2022-06-09  2:22 ` Andrew Morton

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=4884533.31r3eYUQgx@fdefranc-mobl3 \
    --to=fabio.maria.de.francesco@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=fabio.maria.de.francesco@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).