From: KOSAKI Motohiro <kosaki.motohiro@jp•fujitsu.com>
To: liwp.linux@gmail•com
Cc: cl@linux-foundation•org, srikar@linux•vnet.ibm.com,
linux-pci@vger•kernel.org, jbarnes@virtuousgeek•org,
mhocko@suse•cz, paul.gortmaker@windriver•com, hpa@zytor•com,
lwoodman@redhat•com, aarcange@redhat•com, sfr@canb•auug.org.au,
shangw@linux•vnet.ibm.com, x86@kernel•org, hughd@google•com,
mingo@redhat•com, kosaki.motohiro@jp•fujitsu.com,
jan.kiszka@siemens•com, nacc@us•ibm.com, a.p.zijlstra@chello•nl,
mel@csn•ul.ie, jason.wessel@windriver•com,
viro@zeniv•linux.org.uk, bhelgaas@google•com,
cgroups@vger•kernel.org, tglx@linutronix•de,
kamezawa.hiroyu@jp•fujitsu.com, dhowells@redhat•com,
trivial@kernel•org, linux-mm@kvack•org,
linux-kernel@vger•kernel.org, miltonm@bga•com,
minchan@kernel•org, lizefan@huawei•com, hannes@cmpxchg•org,
tj@kernel•org, rientjes@google•com, akpm@linux-foundation•org,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH 7/7] mm/memory.c : cleanup the coding style issue
Date: Fri, 15 Jun 2012 15:40:57 -0400 [thread overview]
Message-ID: <4FDB8FC9.2020909@jp.fujitsu.com> (raw)
In-Reply-To: <1339766449-7835-1-git-send-email-liwp.linux@gmail.com>
> diff --git a/mm/memory.c b/mm/memory.c
> index 1b7dc66..195d6e1 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -2447,7 +2447,8 @@ static inline int pte_unmap_same(struct mm_struct *mm, pmd_t *pmd,
> return same;
> }
>
> -static inline void cow_user_page(struct page *dst, struct page *src, unsigned long va, struct vm_area_struct *vma)
> +static inline void cow_user_page(struct page *dst, struct page *src,
> + unsigned long va, struct vm_area_struct *vma)
> {
> /*
> * If the source page was a PFN mapping, we don't have
Nowadays, many developers prefer to declare a function in one line. and we don't think
this is incorrect anymore. so, I think this is intentional.
prev parent reply other threads:[~2012-06-15 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 13:20 [PATCH 7/7] mm/memory.c : cleanup the coding style issue Wanpeng Li
2012-06-15 19:40 ` KOSAKI Motohiro [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=4FDB8FC9.2020909@jp.fujitsu.com \
--to=kosaki.motohiro@jp$(echo .)fujitsu.com \
--cc=a.p.zijlstra@chello$(echo .)nl \
--cc=aarcange@redhat$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=bhelgaas@google$(echo .)com \
--cc=cgroups@vger$(echo .)kernel.org \
--cc=cl@linux-foundation$(echo .)org \
--cc=dhowells@redhat$(echo .)com \
--cc=hannes@cmpxchg$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=hughd@google$(echo .)com \
--cc=jan.kiszka@siemens$(echo .)com \
--cc=jason.wessel@windriver$(echo .)com \
--cc=jbarnes@virtuousgeek$(echo .)org \
--cc=kamezawa.hiroyu@jp$(echo .)fujitsu.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=liwp.linux@gmail$(echo .)com \
--cc=lizefan@huawei$(echo .)com \
--cc=lwoodman@redhat$(echo .)com \
--cc=mel@csn$(echo .)ul.ie \
--cc=mhocko@suse$(echo .)cz \
--cc=miltonm@bga$(echo .)com \
--cc=minchan@kernel$(echo .)org \
--cc=mingo@redhat$(echo .)com \
--cc=nacc@us$(echo .)ibm.com \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=rientjes@google$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=shangw@linux$(echo .)vnet.ibm.com \
--cc=srikar@linux$(echo .)vnet.ibm.com \
--cc=tglx@linutronix$(echo .)de \
--cc=tj@kernel$(echo .)org \
--cc=trivial@kernel$(echo .)org \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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