From: Yang Fan <nullptr.cpp@gmail.com>
To: akpm@linux-foundation.org, will.deacon@arm.com
Cc: Yang Fan <nullptr.cpp@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] mm/mmap.c: Remove redundant const qualifier of the no-pointer parameters
Date: Sun, 20 Jan 2019 09:13:45 +0100 [thread overview]
Message-ID: <a1ef2a2113cd8847002f0064f198aa4afe465548.1547966629.git.nullptr.cpp@gmail.com> (raw)
In-Reply-To: <cover.1547966629.git.nullptr.cpp@gmail.com>
In according with other functions, remove the const qualifier of the
no-pointer parameters in function arch_get_unmapped_area_topdown().
Signed-off-by: Yang Fan <nullptr.cpp@gmail.com>
---
mm/mmap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/mmap.c b/mm/mmap.c
index f2d163ac827a..84cdde125d4d 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -2127,8 +2127,8 @@ arch_get_unmapped_area(struct file *filp, unsigned long addr,
#ifndef HAVE_ARCH_UNMAPPED_AREA_TOPDOWN
unsigned long
arch_get_unmapped_area_topdown(struct file *filp, unsigned long addr,
- const unsigned long len, const unsigned long pgoff,
- const unsigned long flags)
+ unsigned long len, unsigned long pgoff,
+ unsigned long flags)
{
struct vm_area_struct *vma, *prev;
struct mm_struct *mm = current->mm;
--
2.17.1
next prev parent reply other threads:[~2019-01-20 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 8:12 [PATCH 0/2] mm/mmap.c: Remove some redundancy in arch_get_unmapped_area_topdown() Yang Fan
2019-01-20 8:13 ` [PATCH 1/2] mm/mmap.c: Remove redundant variable 'addr' " Yang Fan
2019-01-23 14:09 ` William Kucharski
2019-01-20 8:13 ` Yang Fan [this message]
2019-01-20 17:09 ` [PATCH 0/2] mm/mmap.c: Remove some redundancy " Mike Rapoport
2019-01-27 4:11 ` [PATCH v2] " Yang Fan
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=a1ef2a2113cd8847002f0064f198aa4afe465548.1547966629.git.nullptr.cpp@gmail.com \
--to=nullptr.cpp@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=will.deacon@arm.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 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.