Tomasz / Mark, On Fri, Jun 7, 2013 at 3:30 AM, Tomasz Figa <tomasz.figa@xxxxxxxxx> wrote: > On Friday 07 of June 2013 11:24:04 Mark Brown wrote: >> On Fri, Jun 07, 2013 at 12:19:58PM +0200, Tomasz Figa wrote: >> > This interesting case makes me think that regulator core should >> > differentiate between regulator lookup failure due to no lookup >> > specified and due to the regulator specified in lookup being >> > unavailable, returning appropriate (different) error codes. >> >> It does exactly that in so far as it can - you get -ENODEV if there's >> definitely no supply and -EPROBE_DEFER otherwise. > > Oh, right, thanks. I somehow felt that it should be doing this already, > but I was looking at 3.9 on Free Electron's LXR. It does so since commit > > 1e4b545cdd regulator: core: return err value for regulator_get if there is > no DT binding Thanks, this is much cleaner. That's what I get for doing the majority of my work on 3.8 at the moment. :-P I will rework the patch and send it out again. -Doug -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
