From: Benjamin Coddington <bcodding@redhat.com>
To: Anna Schumaker <anna@kernel.org>
Cc: Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org, Dai Ngo <dai.ngo@oracle.com>,
Scott Mayhew <smayhew@redhat.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>
Subject: Re: missing patches for v6.6-rc
Date: Wed, 11 Oct 2023 10:01:21 -0400 [thread overview]
Message-ID: <09B062C8-6D70-4BAF-88C0-07A3BA3A36EC@redhat.com> (raw)
In-Reply-To: <CAFX2Jfmrh1YVtf_G1pSsORnF5qVMBjrgMBsS4BWTmx+vLdoAZw@mail.gmail.com>
On 11 Oct 2023, at 9:55, Anna Schumaker wrote:
> Hi Jeff,
>
> On Tue, Oct 10, 2023 at 8:49 AM Jeff Layton <jlayton@kernel.org> wrote:
>>
>> Hi Anna,
>>
>> There are a couple of client side patches that I think we want in v6.6,
>> but that haven't shown up in linux-next yet. Do you still plan to take
>> these from Dai and Scott?
>
> I've pushed out Dai's patch to my linux-next branch, and I can do
> another pull request before the end of the 6.6 cycle. Is Scott's patch
> still needed after your patch "nfs: decrement nrequests counter before
> releasing the req" which went into 6.6-rc5? If so, it doesn't apply
> cleanly on top of the current code so I'll need to fix it up.
Yes, that patch is definitely needed.
Want me to send a current version?
Ben
next prev parent reply other threads:[~2023-10-11 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 12:49 missing patches for v6.6-rc Jeff Layton
2023-10-11 13:55 ` Anna Schumaker
2023-10-11 14:01 ` Benjamin Coddington [this message]
2023-10-11 14:03 ` Anna Schumaker
2023-10-11 14:43 ` [PATCH] NFS: Fix potential oops in nfs_inode_remove_request() Benjamin Coddington
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=09B062C8-6D70-4BAF-88C0-07A3BA3A36EC@redhat.com \
--to=bcodding@redhat.com \
--cc=anna@kernel.org \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.com \
--cc=trond.myklebust@hammerspace.com \
/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.