All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: bad commits in the v9fs tree
Date: Tue, 14 Jun 2022 07:11:21 +0900	[thread overview]
Message-ID: <Yqe2CT0whmf8mYLj@codewreck.org> (raw)
In-Reply-To: <20220614075223.5c2ea764@canb.auug.org.au>

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


      reply	other threads:[~2022-06-13 22:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 21:52 linux-next: bad commits in the v9fs tree Stephen Rothwell
2022-06-13 22:11 ` Dominique Martinet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yqe2CT0whmf8mYLj@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.