From: Li kunyu <kunyu@nfschina.com>
To: peterz@infradead.org
Cc: akpm@linux-foundation.org, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com, kunyu@nfschina.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
luto@kernel.org, mingo@redhat.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: [PATCH] mm: Functions may simplify the use of return values
Date: Mon, 9 May 2022 19:39:19 +0800 [thread overview]
Message-ID: <20220509113920.125795-1-kunyu@nfschina.com> (raw)
In-Reply-To: <20220509071924.GF76023@worktop.programming.kicks-ass.net>
I estimate that this function should not add code in the next year or two.
I consider and optimize this function in terms of code execution efficiency.
There may be a better way.
prev parent reply other threads:[~2022-05-09 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 15:06 Li kunyu
2022-05-09 7:19 ` Peter Zijlstra
2022-05-09 11:39 ` Li kunyu [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=20220509113920.125795-1-kunyu@nfschina.com \
--to=kunyu@nfschina.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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