From: Mukesh Ojha <mojha@codeaurora.org>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Fix build warning
Date: Sat, 30 Mar 2019 23:12:03 +0530 [thread overview]
Message-ID: <91e4d2ab-db8c-aaa4-efbf-5df337242d08@codeaurora.org> (raw)
In-Reply-To: <20190330054248.28357-1-aneesh.kumar@linux.ibm.com>
On 3/30/2019 11:12 AM, Aneesh Kumar K.V wrote:
> mm/debug.c: In function ‘dump_mm’:
> include/linux/kern_levels.h:5:18: warning: format ‘%llx’ expects argument of type ‘long long unsigned int’, but argument 19 has type ‘long int’ [-Wformat=]
> ~~~^
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Does it come even after this patch ?
https://patchwork.kernel.org/patch/10846421/
Thanks.
Mukesh
> ---
> mm/debug.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/debug.c b/mm/debug.c
> index c0b31b6c3877..c134e76918dc 100644
> --- a/mm/debug.c
> +++ b/mm/debug.c
> @@ -137,7 +137,7 @@ void dump_mm(const struct mm_struct *mm)
> "mmap_base %lu mmap_legacy_base %lu highest_vm_end %lu\n"
> "pgd %px mm_users %d mm_count %d pgtables_bytes %lu map_count %d\n"
> "hiwater_rss %lx hiwater_vm %lx total_vm %lx locked_vm %lx\n"
> - "pinned_vm %llx data_vm %lx exec_vm %lx stack_vm %lx\n"
> + "pinned_vm %lx data_vm %lx exec_vm %lx stack_vm %lx\n"
> "start_code %lx end_code %lx start_data %lx end_data %lx\n"
> "start_brk %lx brk %lx start_stack %lx\n"
> "arg_start %lx arg_end %lx env_start %lx env_end %lx\n"
next prev parent reply other threads:[~2019-03-30 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 5:42 [PATCH] mm: Fix build warning Aneesh Kumar K.V
2019-03-30 17:42 ` Mukesh Ojha [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 23:42 [PATCH] mm: fix " hartleys
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=91e4d2ab-db8c-aaa4-efbf-5df337242d08@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.