linux-kernel - Re: [PATCH v3 0/7] clk: replace div_mask() by clk_div

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Mar 2015 18:44:07 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, Sascha Hauer <kernel@...gutronix.de>,
	Peter De Schrijver <pdeschrijver@...dia.com>,
	Tero Kristo <t-kristo@...com>,
	Stephen Boyd <sboyd@...eaurora.org>,
	Dinh Nguyen <dinguyen@...nsource.altera.com>
Subject: Re: [PATCH v3 0/7] clk: replace div_mask() by clk_div_mask()

On Tue, Mar 31, 2015 at 08:22:20PM +0300, Andy Shevchenko wrote:
> This series introduces clk_div_mask() helper in one place instead of div_mask() macros in many clock providers.
> 
> Changelog v3:
> - fix clk_div_mask() prototype: seems tired like on Friday evening!

Yea, that's three versions in the space of half an hour.  Some of
us, who are buried in email, really don't need such stuff filling
our mailboxes with junk like this.

At least build your changes before posting them - or if you haven't
say that you haven't, and then don't worry about it not building.
Don't flood people's mailboxes with three versions of the patches
because they weren't actually ready to be posted.

What this shows is that you should never rush patches out at the
last minute, that's always a recipe for mistakes to be made. :)

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
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/