From: Matthew Wilcox <willy@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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 commits in the folio tree
Date: Tue, 15 Feb 2022 22:54:38 +0000 [thread overview]
Message-ID: <YgwvLi3+p7Olo2uH@casper.infradead.org> (raw)
In-Reply-To: <20220216082951.4bffb750@canb.auug.org.au>
On Wed, Feb 16, 2022 at 08:29:51AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 9864078ecbb0 ("mm/thp: shrink_page_list() avoid splitting VM_LOCKED THP")
> 6a04fcd09a18 ("mm/thp: collapse_file() do try_to_unmap(TTU_BATCH_FLUSH)")
> 52322c19db3b ("mm/munlock: page migration needs mlock pagevec drained")
> fc43a522c2b6 ("mm/munlock: mlock_page() munlock_page() batch by pagevec")
> b60d40429fe9 ("mm/munlock: delete smp_mb() from __pagevec_lru_add_fn()")
> d1dfa0133d1d ("mm/migrate: __unmap_and_move() push good newpage to LRU")
> 27649a0ad4f2 ("mm/munlock: mlock_pte_range() when mlocking or munlocking")
> a098b3660d99 ("mm/munlock: maintain page->mlock_count while unevictable")
> 4aefb923cead ("mm/munlock: replace clear_page_mlock() by final clearance")
> 8a2bfd6e9bc1 ("mm/munlock: rmap call mlock_vma_page() munlock_vma_page()")
> 0942176186ca ("mm/munlock: delete munlock_vma_pages_all(), allow oomreap")
> 190136f4d2e7 ("mm/munlock: delete FOLL_MLOCK and FOLL_POPULATE")
> 9833b8ff6c78 ("mm/munlock: delete page_mlock() and all its works")
>
> are missing a Signed-off-by from their committer.
oh, git-am -s. I'm not used to doing this ;-)
Fixed now. And I fixed sparc32 (differently from the way you had it).
Pushed c306078715cb.
prev parent reply other threads:[~2022-02-15 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 21:29 linux-next: Signed-off-by missing for commits in the folio tree Stephen Rothwell
2022-02-15 22:54 ` Matthew Wilcox [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=YgwvLi3+p7Olo2uH@casper.infradead.org \
--to=willy@infradead.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 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).