From: Michal Hocko <mhocko@kernel.org>
To: Robert Donald Rickett <robert.rickett@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: memory: fixed a coding style issue
Date: Tue, 16 Jan 2018 08:46:56 +0100 [thread overview]
Message-ID: <20180116074656.GA17351@dhcp22.suse.cz> (raw)
In-Reply-To: <20180116011712.eh4dswpm5f7jbeic@shadow1911>
On Mon 15-01-18 19:17:12, Robert Donald Rickett wrote:
> This is a patch to the memory.c file that fixes the
> "ERROR: code indent should use tabs where possible"
> found by the checkpatch.pl tool.
Is this really worth it? The code is not any better readable and it just
adds a churn to the history and makes life of anybody using git blame
slightly more harder. So what is the benefit?
> Signed-off-by: Robert Donald Rickett <robert.rickett@gmail.com>
> ---
> mm/memory.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index ca5674cbaff2..e9f6e58aa77c 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -1663,7 +1663,7 @@ int zap_vma_ptes(struct vm_area_struct *vma, unsigned long address,
> unsigned long size)
> {
> if (address < vma->vm_start || address + size > vma->vm_end ||
> - !(vma->vm_flags & VM_PFNMAP))
> + !(vma->vm_flags & VM_PFNMAP))
> return -1;
> zap_page_range_single(vma, address, size, NULL);
> return 0;
> --
> 2.14.1
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-01-16 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 1:17 Robert Donald Rickett
2018-01-16 7:46 ` Michal Hocko [this message]
[not found] ` <CAE+eAWQEE4FArcspdbZXr=VwpSZ=23hBm7EXByKimPQiNiFKhQ@mail.gmail.com>
2018-01-16 9:26 ` Michal Hocko
2018-01-16 9:31 ` Michal Hocko
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=20180116074656.GA17351@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.rickett@gmail.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
all inboxes | Powered by JetHome®