[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200522154421.GB21655@ict14-OptiPlex-980>
Date: Fri, 22 May 2020 17:44:21 +0200
From: Jonathan Albrieux <jonathan.albrieux@...il.com>
To: Daniel Baluta <daniel.baluta@....com>
Cc: Jonathan Cameron <jic23@...nel.org>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
linux-kernel@...r.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@...r.kernel.org>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH v2 1/4] dt-bindings: iio: imu: bmi160: convert txt format
to yaml
On Fri, May 22, 2020 at 05:59:11PM +0300, Daniel Baluta wrote:
>
> On 22.05.2020 17:26, Jonathan Albrieux wrote:
> > On Fri, May 22, 2020 at 01:47:21PM +0300, Daniel Baluta wrote:
> > > > > > > > +
> > > > > > > > +maintainers:
> > > > > > > > + - can't find a mantainer, author is Daniel Baluta <daniel.baluta@...el.com>
> > > > > > > Daniel is still active in the kernel, just not at Intel any more. +CC
> > > > > > Oh ok thank you! Daniel are you still maintaining this driver?
> > > I can do reviews if requested but I'm not actively maintaining this driver.
> > > If anyone wants
> > >
> > > to take this over, will be more than happy.
> > >
> > >
> > > Other than that we can add my gmail address: Daniel Baluta
> > > <daniel.baluta@...il.com>
> > >
> > >
> > >
> > Well if you'd like to review this patch I'd really appreciate :-)
> > Forgive me for not having understood your answer regarding the maintainer
> > field, can I add you to this binding as maintainer or are you saying to
> > not add you? Thank you and sorry for the repeated question,
> >
> >
>
> OK, so I think would be better not to add me as a maintainer because
>
> this would set some expecation from people, and I most likely won't
>
> have time to met them.
>
>
> Can you instead add the linux-iio mailing list as a maintainer, not sure
>
> if this is a common practice though.
>
>
Ok thank you! I don't know, maybe someone else could point out
the right direction to take, it would be sad to drop yaml documentation
format just for this.
Best regards,
Jonathan Albrieux
Powered by blists - more mailing lists