linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, rppt@kernel.org,
	akpm@linux-foundation.org, broonie@kernel.org,
	Tian Tao <tiantao6@hisilicon.com>,
	linux-arm-kernel@lists.infradead.org, zhangpan26@huawei.com
Cc: Will Deacon <will@kernel.org>,
	kernel-team@android.com, linuxarm@huawei.com
Subject: Re: [PATCH] arm64: mm: Fix missing-prototypes in pageattr.c
Date: Fri, 18 Sep 2020 17:17:18 +0100	[thread overview]
Message-ID: <160043602640.3787797.12531761743096744070.b4-ty@kernel.org> (raw)
In-Reply-To: <1600222847-56792-1-git-send-email-tiantao6@hisilicon.com>

On Wed, 16 Sep 2020 10:20:47 +0800, Tian Tao wrote:
> Fix the following warnings.
> ‘set_memory_valid’ [-Wmissing-prototypes]
> int set_memory_valid(unsigned long addr, int numpages, int enable)
>      ^
> ‘set_direct_map_invalid_noflush’ [-Wmissing-prototypes]
> int set_direct_map_invalid_noflush(struct page *page)
>      ^
> ‘set_direct_map_default_noflush’ [-Wmissing-prototypes]
> int set_direct_map_default_noflush(struct page *page)
>      ^

Applied to arm64 (for-next/misc), thanks!

[1/1] arm64: mm: Fix missing-prototypes in pageattr.c
      https://git.kernel.org/arm64/c/152d75d66428

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2020-09-18 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16  2:20 [PATCH] arm64: mm: Fix missing-prototypes in pageattr.c Tian Tao
2020-09-16  3:34 ` Gavin Shan
2020-09-18 16:17 ` Will Deacon [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=160043602640.3787797.12531761743096744070.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxarm@huawei.com \
    --cc=rppt@kernel.org \
    --cc=tiantao6@hisilicon.com \
    --cc=zhangpan26@huawei.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;
as well as URLs for NNTP newsgroup(s).