linux-kernel - RFC -next: Converting dev_<level> function to return void

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

Message-ID: <1414528393.10912.6.camel@perches.com>
Date:	Tue, 28 Oct 2014 13:33:13 -0700
From:	Joe Perches <joe@...ches.com>
To:	Greg KH <gregkh@...uxfoundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: RFC -next: Converting dev_<level> function to return void

I believe -next currently has no more uses of the dev_<level>
return value, so it's possible to make these return void.

There are dependencies on changes in drivers/net/wireless/ath
that have just been pulled into next-20141028 but not earlier.

Given the dependencies, when would be a good time to submit
changes to these dev_<level> declarations and uses?

It's not urgent, it could wait until 3.19, but maybe sooner
is better.

--
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/