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:	Fri, 17 Oct 2014 09:54:52 -0500
From:	atull <atull@...nsource.altera.com>
To:	Guenter Roeck <linux@...ck-us.net>
CC:	<jdelvare@...e.de>, <lm-sensors@...sensors.org>,
	<lgirdwood@...il.com>, <broonie@...nel.org>, <robh+dt@...nel.org>,
	<pawel.moll@....com>, <mark.rutland@....com>,
	<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
	<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<delicious.quinoa@...il.com>, <dinguyen@...nsource.altera.com>,
	<yvanderv@...nsource.altera.com>
Subject: Re: [PATCH v6 0/4] pmbus: ltc2978: add regulator support

On Thu, 16 Oct 2014, Guenter Roeck wrote:

> On Wed, Oct 15, 2014 at 01:55:06PM -0500, atull@...nsource.altera.com wrote:
> > From: Alan Tull <atull@...nsource.altera.com>
> > 
> > Each output has individual on/off control.
> > 
> > New in v6:
> >   * Much cleanup of the bindings document
> >   * s/vout_en/vout/g
> > 
> > Hopefully this is getting closer.  We will still have the potential problem of
> > repeated node names on boards on boards that have many regulators of the same
> > kind.  If this can be handled in the regulator layer, that might be great.  
> > If we handle it here, whatever we come up with will have to keep the same
> > name over reboots and be predictable enough to serve as regulator node names
> > in the DT.  I'm open for suggestions here.
> > 
> > This patchset now uses "regulator: of: Provide simplified DT parsing method"
> > which are in the next-20141014 tag of linux-next.
> > 
> Hi Alan,
> 
> Since the problems we have seen are in the regulator core code and not
> in your patches, I added the series to -next. I fixed up the 'compatible'
> example in the devicetree description, so there is no need to resubmit
> the patches.
> 
> Thanks,
> Guenter
> 

Hi Guenter,

Thanks!

Alan

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