From: Hugh Dickins <hughd@google•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Hugh Dickins <hughd@google•com>,
Andrew Morton <akpm@linux-foundation•org>,
Matthew Wilcox <willy@infradead•org>,
Vlastimil Babka <vbabka@suse•cz>,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
linux-mm@kvack•org
Subject: Re: linux-next: build warnings after merge of the akpm-current tree
Date: Mon, 28 Mar 2022 12:54:14 -0700 (PDT) [thread overview]
Message-ID: <224c2147-36fe-93ed-41a5-a4609b59b4a2@google.com> (raw)
In-Reply-To: <20220324182725.63a454e3@canb.auug.org.au>
On Thu, 24 Mar 2022, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 9 Feb 2022 17:02:45 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > After merging the akpm-current tree, today's linux-next build (htmldocs)
> > produced these warnings:
> >
> > include/linux/mm_types.h:272: warning: Function parameter or member '__filler' not described in 'folio'
> > include/linux/mm_types.h:272: warning: Function parameter or member 'mlock_count' not described in 'folio'
> >
> > Introduced by commit
> >
> > 60a5c5ab0ba7 ("mm/munlock: maintain page->mlock_count while unevictable")
>
> I am still getting these warnings. That commit is now
>
> 07ca76067308 ("mm/munlock: maintain page->mlock_count while unevictable")
>
> in Linus' tree :-(
Sorry about that Stephen: back in Feb I expected Matthew to have strong
feelings about it, and it wouldn't have been helpful for me to mess it
around at that time.
But I'll reply to this now with my suggested patch: which Matthew may
not like (he may consider it a retrograde step), but unless he NAKs it
and comes up with something we all like better, it should do for now.
I did try to 'make htmldocs' for the first time, but was put off by all
the new packages I was asked to install - not a good use of time. And
I'm so ignorant that I do not even know if "/* public: */" is a helpful
comment or a special annotation.
Patch follows...
Hugh
next prev parent reply other threads:[~2022-03-28 19:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 6:02 linux-next: build warnings after merge of the akpm-current tree Stephen Rothwell
2022-02-09 16:03 ` Hugh Dickins
2022-03-28 23:04 ` Matthew Wilcox
2022-03-29 3:32 ` Hugh Dickins
2022-03-24 7:27 ` Stephen Rothwell
2022-03-28 19:54 ` Hugh Dickins [this message]
2022-03-28 22:10 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2021-10-11 7:31 Stephen Rothwell
2021-10-11 17:46 ` Kees Cook
2021-06-15 10:50 Stephen Rothwell
2020-10-06 12:05 Stephen Rothwell
2020-10-06 20:01 ` Peter Xu
2020-10-06 22:03 ` Stephen Rothwell
2020-01-06 6:14 Stephen Rothwell
2017-08-24 7:41 Stephen Rothwell
2017-08-24 8:15 ` Changwei Ge
2017-08-25 21:23 ` Andrew Morton
2017-08-26 1:23 ` Changwei Ge
2017-03-20 5:22 Stephen Rothwell
2017-03-20 9:05 ` Dmitry Vyukov
2017-03-20 12:30 ` Jan Glauber
2017-03-20 17:06 ` Challa, Mahipal
2015-01-27 8:12 Stephen Rothwell
2015-01-27 8:27 ` Vladimir Davydov
2014-10-03 7:30 Stephen Rothwell
2014-10-03 18:21 ` Andrew Morton
2014-10-03 19:28 ` Michal Nazarewicz
2014-09-23 8:18 Stephen Rothwell
2014-08-26 7:22 Stephen Rothwell
2014-08-26 10:19 ` Xishi Qiu
2013-08-29 9:47 Stephen Rothwell
2013-08-29 11:24 ` Maxim Patlasov
2013-08-29 19:42 ` 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=224c2147-36fe-93ed-41a5-a4609b59b4a2@google.com \
--to=hughd@google$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=vbabka@suse$(echo .)cz \
--cc=willy@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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