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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 8 Sep 2017 17:54:03 +0200 From: Peter Rosin <peda@...ntia.se> To: Hans de Goede <hdegoede@...hat.com> Cc: Stephen Boyd <stephen.boyd@...aro.org>, MyungJoo Ham <myungjoo.ham@...sung.com>, Chanwoo Choi <cw00.choi@...sung.com>, Guenter Roeck <linux@...ck-us.net>, Heikki Krogerus <heikki.krogerus@...ux.intel.com>, Darren Hart <dvhart@...radead.org>, Andy Shevchenko <andy@...radead.org>, Mathias Nyman <mathias.nyman@...el.com>, linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org, devel@...verdev.osuosl.org, Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>, Sathyanarayanan Kuppuswamy Natarajan <sathyaosid@...il.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-usb@...r.kernel.org Subject: Re: [PATCH 1/2] mux: add mux_control_get_optional() API On 2017-09-08 17:45, Peter Rosin wrote: > From: Stephen Boyd <stephen.boyd@...aro.org> > > Sometimes drivers only use muxes under certain scenarios. For > example, the chipidea usb controller may be connected to a usb > switch on some platforms, and connected directly to a usb port on > others. The driver won't know one way or the other though, so add > a mux_control_get_optional() API that allows the driver to > differentiate errors getting the mux from there not being a mux > for the driver to use at all. > --- > Documentation/driver-model/devres.txt | 1 + > drivers/mux/core.c | 104 +++++++++++++++++++++++++++------- > include/linux/mux/consumer.h | 4 ++ > 3 files changed, 89 insertions(+), 20 deletions(-) > > I haven't tested this patch, and hence I have not signed it and I also > removed the sign-off from Stephen... Huh, I definitely intended to mention that this patch is based on [1] from Stephen, but that I've made changes according to the comments in that thread (and more). And those changes are what made me remove the sign-off from Stephen... Sorry for the noise, Peter [1] https://lkml.org/lkml/2017/7/14/655
Powered by blists - more mailing lists