lkml.org 
[lkml]   [2024]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH v1 1/1] gpio: sch: Switch to memory mapped IO accessors
On Wed, Apr 17, 2024 at 11:46 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> On Wed, Apr 17, 2024 at 10:41 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Wed, Apr 17, 2024 at 9:19 PM Bartosz Golaszewski <brgl@bgdevpl> wrote:
> > > On Wed, Apr 17, 2024 at 10:05 AM Andy Shevchenko
> > > <andy.shevchenko@gmail.com> wrote:
> > > > On Wed, Apr 17, 2024 at 12:17 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> > > > > On Sat, Apr 13, 2024 at 10:31 AM William Breathitt Gray <wbg@kernel.org> wrote:

..

> > > > > I applied it as is, if anyone wants it, this can be sent on top of it.
> > > >
> > > > Thanks, but I assumed this should go via my tree and as PR to you. At
> > > > least I have it already in my for-next.
> > >
> > > You didn't respond in any way about picking it up.
> >
> > Hmm... I'm the author of it and I'm a maintainer for that driver. I'm
> > not sure if it's mandatory to respond for that purpose. Usually I
> > asked the opposite, i.e. when I'm not going to pick the thing up.
> >
> > > Can you just drop
> > > it from your branch?
> >
> > It's possible, but I will need to rebase, which is not a good thing to
> > perform. What about just leaving it as is and letting git to (nicely)
> > solve this?
>
> It won't be solved nicely, we'll get a warning about the same commit
> appearing twice with different hashes.

Oh, this sounds like a new check in Linux Next? Or somewhere else?

> Whatever, I dropped it from my tree, it was the HEAD anyway.

Thank you!

--
With Best Regards,
Andy Shevchenko

\
 
 \ /
  Last update: 2024-04-17 22:50    [W:0.035 / U:1.988 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site