From: Greg KH <gregkh@linuxfoundation.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: linux-stable <stable@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Jeff Layton <jlayton@redhat.com>
Subject: Re: [GIT PULL] NFSD fixes for v6.1.y
Date: Tue, 20 Feb 2024 16:19:32 +0100 [thread overview]
Message-ID: <2024022054-cause-suffering-eae8@gregkh> (raw)
In-Reply-To: <4F521AD4-665D-45E2-925A-10E276F29F7E@oracle.com>
On Tue, Feb 20, 2024 at 02:59:40PM +0000, Chuck Lever III wrote:
>
>
> > On Feb 20, 2024, at 9:57 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Feb 20, 2024 at 09:50:53AM -0500, Chuck Lever wrote:
> >> The following changes since commit 8b4118fabd6eb75fed19483b04dab3a036886489:
> >>
> >> Linux 6.1.78 (2024-02-16 19:06:32 +0100)
> >>
> >> are available in the Git repository at:
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git nfsd-6.1.y
> >>
> >> for you to fetch changes up to d432d1006b60bd6b5c38974727bdce78f449eeea:
> >>
> >> nfsd: don't take fi_lock in nfsd_break_deleg_cb() (2024-02-16 13:58:29 -0500)
> >>
> >> ----------------------------------------------------------------
> >> NeilBrown (2):
> >> nfsd: fix RELEASE_LOCKOWNER
> >> nfsd: don't take fi_lock in nfsd_break_deleg_cb()
> >
> > A pull request for just 2 patches? Ok, I'll go dig them out of here,
> > but next time, a mbox or just sending them as patches works too, no need
> > to go through the trouble of this.
>
> Understood. These were already in the repo for our test infrastructure.
Not a problem, if they are easier for you to send this way, that's fine,
they were trivial for me to import in the end, I shouldn't have
complained, I just don't want you to have to do any extra work.
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-20 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 14:50 [GIT PULL] NFSD fixes for v6.1.y Chuck Lever
2024-02-20 14:57 ` Greg KH
2024-02-20 14:59 ` Chuck Lever III
2024-02-20 15:19 ` Greg KH [this message]
2024-02-20 15:01 ` Greg KH
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=2024022054-cause-suffering-eae8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@vger.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).