From: nick <xerofoify@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
mgorman@suse.de, rientjes@google.com, vbabka@suse.cz,
aneesh.kumar@linux.vnet.ibm.com, ebru.akagunduz@gmail.com,
hannes@cmpxchg.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm:Make the function set_recommended_min_free_kbytes have a return type of void
Date: Thu, 02 Jul 2015 09:25:11 -0400 [thread overview]
Message-ID: <55953BB7.70908@gmail.com> (raw)
In-Reply-To: <20150702072302.GA12547@dhcp22.suse.cz>
On 2015-07-02 03:23 AM, Michal Hocko wrote:
> On Wed 01-07-15 13:45:15, Nicholas Krause wrote:
>> This makes the function set_recommended_min_free_kbytes have a
>> return type of void now due to this particular function never
>> needing to signal it's call if it fails due to this function
>> always completing successfully without issue.
>
> The changelog is hard to read for me.
> "
> The function cannot possibly fail so it doesn't make much sense to have
> a return value. Make it void.
> "
> Would sound much easier to parse for me.
>
> I doubt this would help the compiler to generate a better code but in
> general it is better to have void return type when there is no failure
> possible - which is the case here.
>
>> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
>
> Acked-by: Michal Hocko <mhocko@suse.cz>
>
>> ---
>> mm/huge_memory.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>> index c107094..914a72a 100644
>> --- a/mm/huge_memory.c
>> +++ b/mm/huge_memory.c
>> @@ -104,7 +104,7 @@ static struct khugepaged_scan khugepaged_scan = {
>> };
>>
>>
>> -static int set_recommended_min_free_kbytes(void)
>> +static void set_recommended_min_free_kbytes(void)
>> {
>> struct zone *zone;
>> int nr_zones = 0;
>> @@ -139,7 +139,6 @@ static int set_recommended_min_free_kbytes(void)
>> min_free_kbytes = recommended_min;
>> }
>> setup_per_zone_wmarks();
>> - return 0;
>> }
>>
>> static int start_stop_khugepaged(void)
>> --
>> 2.1.4
>>
>
That was exactly my point with these patches readability not compiler improvements.
Otherwise I would have stated that in my commit messages and would argue readability
improvements are important too for the kernel.
Nick
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-07-02 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 17:45 Nicholas Krause
2015-07-02 7:23 ` Michal Hocko
2015-07-02 13:25 ` nick [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=55953BB7.70908@gmail.com \
--to=xerofoify@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=ebru.akagunduz@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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