linux-next: bad commits in the v9fs tree

linux-next: bad commits in the v9fs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 320 bytes --]

Hi all,

Commits

  04608d78b66c ("Linux 5.19-rc1")
  9383b9134c66 ("fix the breakage in close_fd_get_file() calling conventions change")

look like they were rebased or cherry-picked from Linus' tree.from
Linus' tree.  From commits f2906aa86338 and 40a1926022d1 respectively.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: bad commits in the v9fs tree

[Dominique Martinet]

Stephen Rothwell wrote on Tue, Jun 14, 2022 at 07:52:23AM +1000:
>   04608d78b66c ("Linux 5.19-rc1")
>   9383b9134c66 ("fix the breakage in close_fd_get_file() calling conventions change")
> 
> look like they were rebased or cherry-picked from Linus' tree.from
> Linus' tree.  From commits f2906aa86338 and 40a1926022d1 respectively.

Ugh, thank you for noticing.
I had an overly eager `rebase -i` that are usually noop and don't touch
the top patches if left alone, but that only works if no merge is
involved and that wasn't the case here -- I'll be more careful with my
rebase root from now on so it hopefully won't happen again.

Fixed my 9p-next branch so these two should be gone next time you
update.


Thanks,
-- 
Dominique