On Mon, Oct 14, 2019 at 4:28 PM Stephen Boyd <sboyd@xxxxxxxxxx> wrote: > > Quoting Saravana Kannan (2019-10-11 12:15:21) > > The sync_state() driver callback was added recently, but the > > documentation was missing. Adding it now. > > > > Signed-off-by: Saravana Kannan <saravanak@xxxxxxxxxx> > > --- > > .../driver-api/driver-model/driver.rst | 43 +++++++++++++++++++ > > 1 file changed, 43 insertions(+) > > > > diff --git a/Documentation/driver-api/driver-model/driver.rst b/Documentation/driver-api/driver-model/driver.rst > > index 11d281506a04..baa6a85c8287 100644 > > --- a/Documentation/driver-api/driver-model/driver.rst > > +++ b/Documentation/driver-api/driver-model/driver.rst > > @@ -169,6 +169,49 @@ A driver's probe() may return a negative errno value to indicate that > > the driver did not bind to this device, in which case it should have > > released all resources it allocated:: > > > > + void (*sync_state)(struct device *dev); > > This is only in -next as far as I can tell. Will this be combined with a > resend of the patch series that introduces this hook? Based on what Greg said in the other email, I think he's going to pick this up for driver-core-next. -Saravana
