linux-kernel - [PATCH 0/3] ARM: at91/tc/clocksource: various robustness improvements

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1380717265-6497-1-git-send-email-b.brezillon@overkiz.com>
Date:	Wed,  2 Oct 2013 14:34:25 +0200
From:	Boris BREZILLON <b.brezillon@...rkiz.com>
To:	Nicolas Ferre <nicolas.ferre@...el.com>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Thomas Gleixner <tglx@...utronix.de>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Boris BREZILLON <b.brezillon@...rkiz.com>
Subject: [PATCH 0/3] ARM: at91/tc/clocksource: various robustness improvements

Hello,

This series include several improvements regarding the at91 tc clocksource
driver:
 - use clk_prepare/unprepare_enable/disable functions instead of the
   clk_enable/disable functions to prepare the transition to the common clk
   framework
 - check several function return values instead of considering these functions
   always suceed.
 - remove the deprecated IRQF_DISABLED flag

Best Regards,

Boris

Boris BREZILLON (3):
  ARM: at91/tc/clocksource: replace clk_enable/disable with
    clk_prepare_enable/disable_unprepare
  ARM: at91/tc/clocksource: improve driver robustness
  ARM: at91/tc/clocksource: remove IRQF_DISABLED

 drivers/clocksource/tcb_clksrc.c |   61 +++++++++++++++++++++++++++++++-------
 1 file changed, 50 insertions(+), 11 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/