Re: [PATCH 1/6] staging: iio: set proper supply name to devm_regulator_get()

2016-11-05 Thread Jonathan Cameron
On 01/11/16 19:58, Lars-Peter Clausen wrote: > On 11/01/2016 05:03 AM, Matt Ranostay wrote: >> On Mon, Oct 31, 2016 at 10:04 AM, Eva Rachel Retuya >> wrote: >>> The name passed to devm_regulator_get() should match the name of the >>> supply as specified in the device

Re: [PATCH 6/6] staging: iio: ad9832: clean-up regulator 'reg'

2016-11-05 Thread Jonathan Cameron
On 31/10/16 17:04, Eva Rachel Retuya wrote: > Rename regulator 'reg' to 'avdd' so as to be clear what regulator it > stands for specifically. Additionally, get rid of local variable 'reg' > and use direct assignment instead. Update also the goto label pertaining > to the avdd regulator during

Re: [PATCH 5/6] staging: iio: ad9832: add DVDD regulator

2016-11-05 Thread Jonathan Cameron
On 31/10/16 17:04, Eva Rachel Retuya wrote: > The AD9832/AD9835 is supplied with two power sources: AVDD as analog > supply voltage and DVDD as digital supply voltage. > > Attempt to fetch and enable the regulator 'dvdd'. Bail out if any error > occurs. > > Suggested-by: Lars-Peter Clausen

Re: [PATCH 3/6] staging: iio: ad7192: add DVdd regulator

2016-11-05 Thread Jonathan Cameron
On 31/10/16 17:04, Eva Rachel Retuya wrote: > The AD7190/AD7192/AD7193/AD7195 is supplied with two power sources: > AVdd as analog supply voltage and DVdd as digital supply voltage. > > Attempt to fetch and enable the regulator 'dvdd'. Bail out if any error > occurs. > > Suggested-by: Lars-Peter

Re: [PATCH 1/6] staging: iio: set proper supply name to devm_regulator_get()

2016-11-05 Thread Jonathan Cameron
On 05/11/16 12:58, Jonathan Cameron wrote: > On 01/11/16 19:58, Lars-Peter Clausen wrote: >> On 11/01/2016 05:03 AM, Matt Ranostay wrote: >>> On Mon, Oct 31, 2016 at 10:04 AM, Eva Rachel Retuya >>> wrote: The name passed to devm_regulator_get() should match the name of

Re: [PATCH 1/6] staging: iio: set proper supply name to devm_regulator_get()

2016-11-05 Thread Jonathan Cameron
On 31/10/16 17:04, Eva Rachel Retuya wrote: > The name passed to devm_regulator_get() should match the name of the > supply as specified in the device datasheet. This makes it clear what > power supply is being referred to in case of presence of other > regulators. > > Currently, the supply name

Re: [PATCH 4/6] staging: iio: ad7192: rename regulator 'reg' to 'avdd'

2016-11-05 Thread Jonathan Cameron
On 31/10/16 17:04, Eva Rachel Retuya wrote: > Rename regulator 'reg' to 'avdd' so as to be clear what regulator it > stands for specifically. Also, update the goto label accordingly. > > Signed-off-by: Eva Rachel Retuya Applied. Thanks, Jonathan > --- >

[PATCH] ssb: Fix error routine when fallback SPROM fails

2016-11-05 Thread Larry Finger
When there is a CRC error in the SPROM read from the device, the code attempts to handle a fallback SPROM. When this also fails, the driver returns zero rather than an error code. Signed-off-by: Larry Finger Cc: Stable --- drivers/ssb/pci.c |

[PATCH] Staging: vme: vme_pio2: Prefer using the BIT macro

2016-11-05 Thread Shiva Kerdel
Replace all occurences of (1 << x) by BIT(x) in the file vme_pio2.h to get rid of checkpatch.pl "check" output "Prefer using the BIT macro". Signed-off-by: Shiva Kerdel --- drivers/staging/vme/devices/vme_pio2.h | 86 +- 1 file changed, 43

销售业务公关策略快速突破强化训练

2016-11-05 Thread 林山蓁
如何成为优秀的销售顾问.xls Description: Binary data ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Re: Greybus Future

2016-11-05 Thread Greg KH
On Tue, Nov 01, 2016 at 12:13:06PM -0700, Joël Porquet wrote: > I don't have much hope but would there be a way to find out whether > all the code that was developed between the moment we stopped using > github and the project was canceled could be pushed back to github? > > It seems like it

Re: [PATCH 2/6] staging: iio: rework regulator handling

2016-11-05 Thread Jonathan Cameron
On 31/10/16 17:04, Eva Rachel Retuya wrote: > Currently, the affected drivers ignore all errors from regulator_get(). > The way it is now, it also breaks probe deferral (EPROBE_DEFER). The > correct behavior is to propagate the error to the upper layers so they > can handle it accordingly. > >