From: Mike Snitzer <snitzer@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Trond Myklebust <trondmy@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Christian Brauner <brauner@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-nfs@vger.kernel.org
Subject: Re: [6.19 PATCH] nfs/localio: fix regression due to out-of-order __put_cred [was: Re: linux-next: manual merge of the nfs tree with Linus' tree]
Date: Fri, 5 Dec 2025 21:23:27 -0500 [thread overview]
Message-ID: <aTOTn3n-0V42j8he@kernel.org> (raw)
In-Reply-To: <CAHk-=wj3B1-nZ-4jUP0FsLH4f1bbpO=Q9J88Ziz=wxE-Jm-skw@mail.gmail.com>
On Fri, Dec 05, 2025 at 05:55:50PM -0800, Linus Torvalds wrote:
> On Fri, 5 Dec 2025 at 17:32, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Let me do that once I finish my "merge various architecture updates".
> > I'm almost done with that side - just one more SoC pull to go, I think
> > - and can go back to looking at filesystem changes.
>
> Ok, done and pushed out. Can you please verify that the current git
> tree looks like you expected?
Looks good. Thanks
prev parent reply other threads:[~2025-12-06 2:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 0:19 linux-next: manual merge of the nfs tree with Linus' tree Stephen Rothwell
2025-12-05 0:34 ` Trond Myklebust
2025-12-05 1:11 ` Mike Snitzer
2025-12-05 1:08 ` [6.19 PATCH] nfs/localio: fix regression due to out-of-order __put_cred [was: Re: linux-next: manual merge of the nfs tree with Linus' tree] Mike Snitzer
2025-12-05 10:08 ` Christian Brauner
2025-12-06 0:01 ` Trond Myklebust
2025-12-06 0:32 ` Trond Myklebust
2025-12-06 0:36 ` Mike Snitzer
2025-12-06 1:32 ` Linus Torvalds
2025-12-06 1:55 ` Linus Torvalds
2025-12-06 2:23 ` Mike Snitzer [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=aTOTn3n-0V42j8he@kernel.org \
--to=snitzer@kernel.org \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=trondmy@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).