[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=Mdt0D4L17St06nn=mCuObG=e3btf42NHfsuTEOQepB6bQ@mail.gmail.com>
Date: Fri, 15 Nov 2024 07:23:21 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Andi Shyti <andi.shyti@...nel.org>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>, linux-arm-msm@...r.kernel.org,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] i2c: qup: use generic device property accessors
On Thu, Nov 14, 2024 at 11:52 PM Dmitry Baryshkov
<dmitry.baryshkov@...aro.org> wrote:
>
> On Wed, Nov 13, 2024 at 04:39:23PM +0100, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> >
> >
> > On Tue, 08 Oct 2024 18:09:47 +0200, Bartosz Golaszewski wrote:
> > > There's no reason for this driver to use OF-specific property helpers.
> > > Drop the last one in favor of the generic variant and no longer include
> > > of.h.
> > >
> > >
> >
> > Applied, to the GPIO tree as the maintainer has been unresposive for two
> > months and the change is trivial.
> >
> > [1/1] i2c: qup: use generic device property accessors
> > commit: 400913bd4edd76ef1775bfd95543846bd6f5ed71
>
> I think it's a bad idea to pull unrelated patches just because you have
> a GPIO tree.
>
I know. I dropped it. But I have no idea what the recourse is if you
have reviewed trivial refactorings that get stuck on the list forever
because the maintainer whose address otherwise doesn't bounce and who
is active on the list just chooses not to respond for weeks. There
don't seem to be written rules on this.
Greg: Can you take it instead?
Bart
Powered by blists - more mailing lists