From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] include: asm-generic: page.h: Remove useless get_user_page and free_user_page
Date: Thu, 19 Nov 2015 11:44:34 +0530 [thread overview]
Message-ID: <564D68CA.6010708@synopsys.com> (raw)
In-Reply-To: <COL130-W7B5F0BB94C76AF6B12EA7B91C0@phx.gbl>
On Thursday 19 November 2015 01:10 AM, Chen Gang wrote:
> From ba7c00c4cb976109b6a35812ce9649aaeda81e2d Mon Sep 17 00:00:00 2001
> From: Chen Gang <gang.chen.5i5j@gmail.com>
> Date: Thu, 19 Nov 2015 03:24:42 +0800
> Subject: [PATCH] include: asm-generic: page.h: Remove useless get_user_page and free_user_page
>
> They are not symmetric with each other, neither are used in real world
> (can not be found by grep command in source code root directory), so
> remove them.
>
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
> ---
> arch/arc/include/asm/page.h | 3 ---
> arch/arm/include/asm/page-nommu.h | 3 ---
> arch/frv/include/asm/page.h | 3 ---
> arch/m68k/include/asm/page_mm.h | 3 ---
> arch/m68k/include/asm/page_no.h | 3 ---
> arch/openrisc/include/asm/page.h | 3 ---
> include/asm-generic/page.h | 3 ---
> 7 files changed, 21 deletions(-)
So this is one huge patch touching several arches with potential to cause
conflicts when merged. Can u divy them up and then the maintainers can simply
merge them individually given there is no common dependency !
next prev parent reply other threads:[~2015-11-19 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 19:40 [PATCH] include: asm-generic: page.h: Remove useless get_user_page and free_user_page Chen Gang
2015-11-19 0:11 ` Russell King - ARM Linux
2015-11-19 6:14 ` Vineet Gupta [this message]
2015-11-19 11:25 ` Arnd Bergmann
2015-11-19 16:18 ` Russell King - ARM Linux
2015-11-19 16:35 ` Arnd Bergmann
2015-11-19 18:59 ` Chen Gang
2015-11-20 12:15 ` Greg Ungerer
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=564D68CA.6010708@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.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 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).