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] [day] [month] [year] [list]
Message-ID: <CACRpkdak-BOEwZWCn+XCb8as0EudM4BAyMjMUW4bsYmrcO6=6A@mail.gmail.com>
Date:	Mon, 8 Jun 2015 15:36:10 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	Sören Brinkmann <soren.brinkmann@...inx.com>,
	Arnd Bergmann <arnd@...db.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] pinctrl: add pinctrl_register_reason() to return proper
 error code

On Tue, Jun 2, 2015 at 5:32 PM, Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:

> If nobody is opposed to this, I can send a single big patch
> replacing all the references.
>
> In that case, we would not need _strict().

Yeah just do this.

> My concern is the sudden change of the function interface
> will break drivers that are under development out of the source tree.

Base the patch on my -devel branch so you cover all driver in
development. I will deal with any resulting mess.

Out of tree drivers we do not take into account, they should focus
their efforts on working upstream.

Yours,
Linus Walleij
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ