From: Tejun Heo <tj@kernel.org>
To: Sean Fu <fxinrong@gmail.com>
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] workqueue: Use IS_ERR and PTR_ERR instead of PTR_ERR_OR_ZERO.
Date: Tue, 5 May 2020 11:56:49 -0400 [thread overview]
Message-ID: <20200505155649.GE12217@mtj.thefacebook.com> (raw)
In-Reply-To: <20200429040413.13942-1-fxinrong@gmail.com>
On Wed, Apr 29, 2020 at 12:04:13PM +0800, Sean Fu wrote:
> Replace inline function PTR_ERR_OR_ZERO with IS_ERR and PTR_ERR to
> remove redundant parameter definitions and checks.
> Reduce code size.
> Before:
> text data bss dec hex filename
> 47510 5979 840 54329 d439 kernel/workqueue.o
> After:
> text data bss dec hex filename
> 47474 5979 840 54293 d415 kernel/workqueue.o
>
> Signed-off-by: Sean Fu <fxinrong@gmail.com>
Applied to wq/for-5.8.
Thanks.
--
tejun
prev parent reply other threads:[~2020-05-05 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 2:19 [PATCH] workqueue: Use IS_ERR and PTR_ERR instead of PTR_ERR_OR_ZERO to remove redundant definitions and checks Sean Fu
2020-04-29 4:04 ` [PATCH v2] workqueue: Use IS_ERR and PTR_ERR instead of PTR_ERR_OR_ZERO Sean Fu
2020-05-05 15:56 ` Tejun Heo [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=20200505155649.GE12217@mtj.thefacebook.com \
--to=tj@kernel.org \
--cc=fxinrong@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.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