From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kernel test robot <lkp@intel.com>, Christoph Hellwig <hch@lst.de>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Logan Gunthorpe <logang@deltatee.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Dan Williams <dan.j.williams@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [hnaz-mm:master 237/343] arch/powerpc/mm/book3s64/pgtable.c:540:15: warning: no previous prototype for 'memremap_compat_align'
Date: Thu, 17 Feb 2022 22:07:07 +0000 [thread overview]
Message-ID: <Yg7HC3r1mdvsHs4s@casper.infradead.org> (raw)
In-Reply-To: <20220217125553.88a9ce7723ea8fd39c76a199@linux-foundation.org>
On Thu, Feb 17, 2022 at 12:55:53PM -0800, Andrew Morton wrote:
> On Fri, 18 Feb 2022 03:46:17 +0800 kernel test robot <lkp@intel.com> wrote:
> > >> arch/powerpc/mm/book3s64/pgtable.c:540:15: warning: no previous prototype for 'memremap_compat_align' [-Wmissing-prototypes]
> > 540 | unsigned long memremap_compat_align(void)
> > | ^~~~~~~~~~~~~~~~~~~~~
>
> Thanks, I did this.
I guess this is now my responsibility? Folded that fix in and pushed
out 8cbcadaf5aef to infradead/for-next
> --- a/arch/powerpc/mm/book3s64/pgtable.c~mm-dont-include-linux-memremaph-in-linux-mmh-fix-2-fix
> +++ a/arch/powerpc/mm/book3s64/pgtable.c
> @@ -6,6 +6,7 @@
> #include <linux/sched.h>
> #include <linux/mm_types.h>
> #include <linux/memblock.h>
> +#include <linux/memremap.h>
> #include <linux/debugfs.h>
> #include <misc/cxl-base.h>
>
> _
>
>
>
prev parent reply other threads:[~2022-02-17 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 19:46 kernel test robot
2022-02-17 20:55 ` Andrew Morton
2022-02-17 22:07 ` 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=Yg7HC3r1mdvsHs4s@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=hannes@cmpxchg.org \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=logang@deltatee.com \
/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