On Wed, Apr 17, 2024 at 10:41 PM Andy Shevchenko <andy.shevchenko@xxxxxxxxx> wrote: > > On Wed, Apr 17, 2024 at 9:19 PM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > > On Wed, Apr 17, 2024 at 10:05 AM Andy Shevchenko > > <andy.shevchenko@xxxxxxxxx> wrote: > > > On Wed, Apr 17, 2024 at 12:17 AM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > > > > On Sat, Apr 13, 2024 at 10:31 AM William Breathitt Gray <wbg@xxxxxxxxxx> 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? > > -- > With Best Regards, > Andy Shevchenko It won't be solved nicely, we'll get a warning about the same commit appearing twice with different hashes. Whatever, I dropped it from my tree, it was the HEAD anyway. Bart