On Sun, Oct 09, 2022 at 01:24:21PM +0100, Jonathan Cameron wrote: > On Thu, 6 Oct 2022 19:17:39 +0300 > Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > On Thu, Oct 06, 2022 at 05:36:52PM +0300, Matti Vaittinen wrote: ... > > > (cherry picked from commit b6058e052b842a19c8bb639798d8692cd0e7589f) > > > > Not sure: > > - why this is in the commit message > > - what it points to, since > > $ git show b6058e052b842a19c8bb639798d8692cd0e7589f > > fatal: bad object b6058e052b842a19c8bb639798d8692cd0e7589f > > These are now upstream in Linus' tree and in my testing branch. I don't see them. As I pointed out the commit IDs are not in the any of the official trees (subsystem maintainer's or Linus'). Again, read my doubts about the above commit message. > I'd not normally advocate working on top of that (because I rebase it), but > if it is useful for this series go ahead. > > > Already in Mark's regulator tree. Not to be merged. Included just for > > > the sake of the completeness. Will be dropped when series is rebased on > > > top of the 6.1-rc1 > > > > Ah, I see, but does it mean the commit has been rebased or you used wrong SHA? -- With Best Regards, Andy Shevchenko
