From: Pan Xinhui <xinhuix.pan@intel.com>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>, "bp@suse.de" <bp@suse.de>,
"Kani, Toshimitsu" <toshi.kani@hp.com>,
"jgross@suse.com" <jgross@suse.com>,
"mcgrof@suse.com" <mcgrof@suse.com>,
"mnipxh@163.com" <mnipxh@163.com>,
"yanmin_zhang@linux.intel.com" <yanmin_zhang@linux.intel.com>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH V4] x86/mm/pat: Do a small optimization and fix in reserve_memtype
Date: Thu, 23 Jul 2015 09:55:47 +0800 [thread overview]
Message-ID: <55B049A3.1020503@intel.com> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B40295AA03106@G9W0745.americas.hpqcorp.net>
hi, Elliot
thanks for your reply.
On 2015年07月22日 22:38, Elliott, Robert (Server Storage) wrote:
>
>
> ---
> Robert Elliott, HP Server Storage
>
>> -----Original Message-----
>> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
>> owner@vger.kernel.org] On Behalf Of Pan Xinhui
>> Sent: Wednesday, July 22, 2015 8:27 AM
> ...
>> diff --git a/arch/x86/mm/pat.c b/arch/x86/mm/pat.c
>> index 188e3e0..8fa1f07 100644
>> --- a/arch/x86/mm/pat.c
>> +++ b/arch/x86/mm/pat.c
>> @@ -521,10 +521,7 @@ int reserve_memtype(u64 start, u64 end, enum
>> page_cache_mode req_type,
>>
>> is_range_ram = pat_pagerange_is_ram(start, end);
>> if (is_range_ram == 1) {
>> -
>> - err = reserve_ram_pages_type(start, end, req_type, new_type);
>> -
>> - return err;
>> + return reserve_ram_pages_type(start, end, req_type, new_type);
>> } else if (is_range_ram < 0) {
>> return -EINVAL;
>> }
>
> With each branch now just one line, the {} can be removed.
>
thanks for the nice tips. sorry for my mistakes.
thanks
xinhui
>
>
prev parent reply other threads:[~2015-07-23 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 13:27 [PATCH V4] x86/mm/pat: Do a small optimization and fix in reserve_memtype Pan Xinhui
2015-07-22 14:38 ` Elliott, Robert (Server Storage)
2015-07-22 14:45 ` Borislav Petkov
2015-07-23 2:00 ` Pan Xinhui
2015-07-23 1:55 ` Pan Xinhui [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=55B049A3.1020503@intel.com \
--to=xinhuix.pan@intel.com \
--cc=Elliott@hp.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=mingo@redhat.com \
--cc=mnipxh@163.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.com \
--cc=x86@kernel.org \
--cc=yanmin_zhang@linux.intel.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