From: Viresh Kumar <viresh.kumar@linaro.org>
To: akpm@linux-foundation.org
Cc: linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V1 Resend 00/11] vial: Drop unlikely before IS_ERR(_OR_NULL)
Date: Mon, 10 Aug 2015 11:42:22 +0530 [thread overview]
Message-ID: <cover.1439187003.git.viresh.kumar@linaro.org> (raw)
Hi Andrew,
This cleans up the usage of IS_ERR(_OR_NULL)(), where the callers have
added additional unlikely compiler flag to them. It also fixes the
definition of IS_ERR_OR_NULL(), to use unlikely for all checks it does.
V1->V2:
- Some of the patches are already applied
- Dropped input subsystem patch as Dmitry thought its more readable
currently.
Viresh Kumar (11):
err.h: add (missing) unlikely() to IS_ERR_OR_NULL()
PM / OPP: Drop unlikely before IS_ERR(_OR_NULL)
drivers: devfreq: Drop unlikely before IS_ERR(_OR_NULL)
drivers: md: Drop unlikely before IS_ERR(_OR_NULL)
drivers: misc: Drop unlikely before IS_ERR(_OR_NULL)
drivers: net: Drop unlikely before IS_ERR(_OR_NULL)
drivers: rtc: Drop (un)likely before IS_ERR(_OR_NULL)
fs: Drop unlikely before IS_ERR(_OR_NULL)
blk-cgroup: Drop unlikely before IS_ERR(_OR_NULL)
mm: Drop unlikely before IS_ERR(_OR_NULL)
net: Drop unlikely before IS_ERR(_OR_NULL)
drivers/base/power/opp.c | 6 +++---
drivers/devfreq/devfreq.c | 4 ++--
drivers/md/dm-snap-persistent.c | 2 +-
drivers/md/dm-verity.c | 2 +-
drivers/md/persistent-data/dm-block-manager.c | 8 ++++----
drivers/misc/c2port/core.c | 2 +-
drivers/net/ethernet/ti/netcp_core.c | 4 ++--
drivers/rtc/interface.c | 2 +-
drivers/rtc/rtc-bfin.c | 2 +-
drivers/rtc/rtc-gemini.c | 2 +-
fs/cifs/readdir.c | 2 +-
fs/ecryptfs/inode.c | 2 +-
fs/ext4/extents.c | 6 +++---
fs/ext4/namei.c | 2 +-
fs/namei.c | 4 ++--
fs/ncpfs/dir.c | 2 +-
fs/nfs/objlayout/objio_osd.c | 2 +-
fs/proc/proc_sysctl.c | 2 +-
include/linux/blk-cgroup.h | 2 +-
include/linux/err.h | 2 +-
mm/huge_memory.c | 2 +-
net/openvswitch/datapath.c | 2 +-
net/sctp/socket.c | 2 +-
net/socket.c | 6 +++---
24 files changed, 36 insertions(+), 36 deletions(-)
--
2.4.0
next reply other threads:[~2015-08-10 6:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 6:12 Viresh Kumar [this message]
2015-08-10 6:12 ` [PATCH V1 Resend 01/11] err.h: add (missing) unlikely() to IS_ERR_OR_NULL() Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 02/11] PM / OPP: Drop unlikely before IS_ERR(_OR_NULL) Viresh Kumar
2015-08-10 21:15 ` Pavel Machek
2015-08-10 6:12 ` [PATCH V1 Resend 03/11] drivers: devfreq: " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 04/11] drivers: md: " Viresh Kumar
2015-08-10 20:05 ` Mike Snitzer
2015-08-11 1:42 ` Viresh Kumar
2015-08-11 2:43 ` Mike Snitzer
2015-08-10 6:12 ` [PATCH V1 Resend 05/11] drivers: misc: " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 06/11] drivers: net: " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 07/11] drivers: rtc: Drop (un)likely " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 08/11] fs: Drop unlikely " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 09/11] blk-cgroup: " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 10/11] mm: " Viresh Kumar
2015-08-10 6:12 ` [PATCH V1 Resend 11/11] net: " Viresh Kumar
2015-08-10 11:51 ` Neil Horman
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=cover.1439187003.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=linaro-kernel@lists.linaro.org \
--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