On Thu, Aug 15, 2024 at 03:51:41PM +0100, Mark Rutland wrote: > On Mon, Aug 12, 2024 at 05:03:45PM +0200, Greg KH wrote: > > On Fri, Aug 09, 2024 at 10:57:45AM +0100, Mark Rutland wrote: > > > [ Upstream commit b0672bbe133ebb6f7be21fce1d742d52f25bcdc7 ] > > > > Now I figured it out, this is the wrong git id, and is not in any tree > > anywhere. It should be adeec61a4723fd3e39da68db4cc4d924e6d7f641. > > > > I'll go hand-edit it now... > > Thanks, and sorry about that. > > Looking in my local tree, the incorrect commit id is a copy of > adeec61a4723fd3e39da68db4cc4d924e6d7f641 where the earlier commits had > been updated with "[ Upstream commit XXX ]" wording. Evidently I grabbed > the commit ID from the wrong branch when I was folding that in. > > I'll try to make sure that doesn't happen again. Is there any public > tooling for sanity-checking this? Not that I know of :(
