lkml.org 
[lkml]   [2022]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v1 2/2] gpiolib: Introduce gpio_device_get() and gpio_device_put()
On Tue, Nov 29, 2022 at 04:49:34PM +0100, Bartosz Golaszewski wrote:
> On Tue, Nov 29, 2022 at 3:47 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Tue, Nov 29, 2022 at 02:54:10PM +0100, Bartosz Golaszewski wrote:
> > > On Fri, Nov 25, 2022 at 7:11 PM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > >
> > > > Introduce gpio_device_get() and gpio_device_put() helpers
> > > > and convert existing users.
> >
> > > This doesn't apply to my for-next branch, can you rebase and resend
> > > (just this one, the other is applied).
> >
> > The problem is that you don't merge or cherry-pick fixes into your
> > for-next branch and they are getting diverged.
> >
> > In PDx86 subsystem we decided to cherry-pick the fixes into for-next.
> > Some other subsystems are doing back-merges (but I remember that Linus
> > T. complained about back merges, although I dunno if it's still
> > the case). Some subsystems merges their fixes into for-next, dunno
> > if it's the best practice either.
> >
> > That said, this can be submitted after v6.2-rc1 is out.
>
> I do merge tags if I need to. Normally you'd mention any requirements
> for the series in the cover letter.

It's my fault. But thanks for clarifying the process.

> I have not sent any fixes so far in this release cycle BTW.

Yes, that's now obvious...

--
With Best Regards,
Andy Shevchenko


\
 
 \ /
  Last update: 2022-11-29 17:22    [W:0.054 / U:0.500 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site