Re: [PATCH v3 01/10] Add auxiliary bus support

[Leon Romanovsky]

On Sat, Nov 14, 2020 at 12:21:39AM +0100, Greg KH wrote:
> On Fri, Nov 13, 2020 at 04:07:57PM +0000, Ertman, David M wrote:
> > > -----Original Message-----
> > > From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
> > > Sent: Friday, November 13, 2020 7:50 AM
> > > To: Ertman, David M <david.m.ertman@xxxxxxxxx>
> > > Cc: alsa-devel@xxxxxxxxxxxxxxxx; tiwai@xxxxxxx; broonie@xxxxxxxxxx; linux-
> > > rdma@xxxxxxxxxxxxxxx; jgg@xxxxxxxxxx; dledford@xxxxxxxxxx;
> > > netdev@xxxxxxxxxxxxxxx; davem@xxxxxxxxxxxxx; kuba@xxxxxxxxxx;
> > > ranjani.sridharan@xxxxxxxxxxxxxxx; pierre-louis.bossart@xxxxxxxxxxxxxxx;
> > > fred.oh@xxxxxxxxxxxxxxx; parav@xxxxxxxxxxxx; Saleem, Shiraz
> > > <shiraz.saleem@xxxxxxxxx>; Williams, Dan J <dan.j.williams@xxxxxxxxx>;
> > > Patil, Kiran <kiran.patil@xxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx;
> > > leonro@xxxxxxxxxx
> > > Subject: Re: [PATCH v3 01/10] Add auxiliary bus support
> > >
> > > On Thu, Oct 22, 2020 at 05:33:29PM -0700, Dave Ertman wrote:
> > > > Add support for the Auxiliary Bus, auxiliary_device and auxiliary_driver.
> > > > It enables drivers to create an auxiliary_device and bind an
> > > > auxiliary_driver to it.
> > > >
> > > > The bus supports probe/remove shutdown and suspend/resume callbacks.
> > > > Each auxiliary_device has a unique string based id; driver binds to
> > > > an auxiliary_device based on this id through the bus.
> > > >
> > > > Co-developed-by: Kiran Patil <kiran.patil@xxxxxxxxx>
> > > > Signed-off-by: Kiran Patil <kiran.patil@xxxxxxxxx>
> > > > Co-developed-by: Ranjani Sridharan <ranjani.sridharan@xxxxxxxxxxxxxxx>
> > > > Signed-off-by: Ranjani Sridharan <ranjani.sridharan@xxxxxxxxxxxxxxx>
> > > > Co-developed-by: Fred Oh <fred.oh@xxxxxxxxxxxxxxx>
> > > > Signed-off-by: Fred Oh <fred.oh@xxxxxxxxxxxxxxx>
> > > > Co-developed-by: Leon Romanovsky <leonro@xxxxxxxxxx>
> > > > Signed-off-by: Leon Romanovsky <leonro@xxxxxxxxxx>
> > > > Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@xxxxxxxxxxxxxxx>
> > > > Reviewed-by: Shiraz Saleem <shiraz.saleem@xxxxxxxxx>
> > > > Reviewed-by: Parav Pandit <parav@xxxxxxxxxxxx>
> > > > Reviewed-by: Dan Williams <dan.j.williams@xxxxxxxxx>
> > > > Signed-off-by: Dave Ertman <david.m.ertman@xxxxxxxxx>
> > > > ---
> > >
> > > Is this really the "latest" version of this patch submission?
> > >
> > > I see a number of comments on it already, have you sent out a newer one,
> > > or is this the same one that the mlx5 driver conversion was done on top
> > > of?
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > V3 is the latest sent so far.  There was a suggestion that v3 might be merged and
> > the documentation changes could be in a follow up patch.  I have those changes done
> > and ready though, so no reason not to merge them in and do a resend.
> >
> > Please expect v4 in just a little while.
>
> Thank you, follow-up patches aren't usually a good idea :)

The changes were in documentation area that will be changed
anyway after dust will settle and we all see real users and
more or less stable in-kernel API.

Thanks