| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1355852048-23188-1-git-send-email-linux@prisktech.co.nz> Date: Wed, 19 Dec 2012 06:34:02 +1300 From: Tony Prisk <linux@...sktech.co.nz> To: kernel-janitors@...r.kernel.org Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Tony Prisk <linux@...sktech.co.nz> Subject: [PATCH RESEND 0/6] Remove incorrect usage of IS_ERR_OR_NULL on clk_get Resend to include mailing lists. As per the kernel docs, clk_get() cannot return NULL. * clk_get - lookup and obtain a reference to a clock producer. * @dev: device for clock "consumer" * @id: clock consumer ID * * Returns a struct clk corresponding to the clock producer, or * valid IS_ERR() condition containing errno. This patch set replaces instances of IS_ERR_OR_NULL tests againt clk_get() results with IS_ERR tests. Tony Prisk (6): clk: omap: Fix incorrect usage of IS_ERR_OR_NULL clk: exynos: Fix incorrect usage of IS_ERR_OR_NULL clk: exynos: Fix incorrect usage of IS_ERR_OR_NULL clk: s5p-tv: Fix incorrect usage of IS_ERR_OR_NULL clk: s5p-fimc: Fix incorrect usage of IS_ERR_OR_NULL clk: s5p-g2d: Fix incorrect usage of IS_ERR_OR_NULL arch/arm/plat-omap/dmtimer.c | 6 +++--- drivers/gpu/drm/exynos/exynos_hdmi.c | 10 +++++----- drivers/gpu/drm/exynos/exynos_mixer.c | 14 +++++++------- drivers/media/platform/s5p-fimc/fimc-mdevice.c | 2 +- drivers/media/platform/s5p-g2d/g2d.c | 4 ++-- drivers/media/platform/s5p-tv/hdmi_drv.c | 10 +++++----- drivers/media/platform/s5p-tv/mixer_drv.c | 10 +++++----- drivers/media/platform/s5p-tv/sdo_drv.c | 10 +++++----- 8 files changed, 33 insertions(+), 33 deletions(-) -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists