[PATCH V1 Resend 00/10] trivial: Drop unlikely before IS_ERR(_OR_NULL)

[Viresh Kumar]

Hi Jiri,

Andrew Morton suggested to take these patches through your tree and so
another resend.

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.

Viresh Kumar (10):
  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: 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/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 +++---
 21 files changed, 30 insertions(+), 30 deletions(-)

-- 
2.4.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/