linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: 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>,
	Joe Perches <joe@perches.com>,
	Miles Chen <miles.chen@mediatek.com>,
	Mike Rapoport <rppt@kernel.org>
Subject: Re: linux-next: Signed-off-bys missing for commits in the akpm-current tree
Date: Fri, 8 May 2020 17:36:27 -0700	[thread overview]
Message-ID: <20200508173627.eda3f18b808dd6728a273d8b@linux-foundation.org> (raw)
In-Reply-To: <20200509101919.36231cf9@canb.auug.org.au>

On Sat, 9 May 2020 10:19:19 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> Commits
> 
>   a41ffad2df78 ("mm: free_area_init: allow defining max_zone_pfn in descending order")

Look OK to me?

https://ozlabs.org/~akpm/mmotm/broken-out/mm-free_area_init-allow-defining-max_zone_pfn-in-descending-order.patch

>   ed1e07587fb4 ("mm/gup.c: further document vma_permits_fault()")

Yeah, I wasn't sent a signoff.  Miles, please send?

>   da5d272cd01a ("checkpatch: test $GIT_DIR changes")

Yup, that's a play patch which I'm supposed to test.

> are missing a Signed-off-by from their authors (I haven't reported the
> -fix patches).
> 
> I guess the first one is actually a fix patch and will be rolled into
> its parent.
> 
> Also, the Link tag in this last one is invalid :-(

Private email ;).  If my testing is successful I guess we'll get a real
version of this.


      reply	other threads:[~2020-05-09  0:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09  0:19 linux-next: Signed-off-bys missing for commits in the akpm-current tree Stephen Rothwell
2020-05-09  0:36 ` Andrew Morton [this message]

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=20200508173627.eda3f18b808dd6728a273d8b@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=miles.chen@mediatek.com \
    --cc=rppt@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).