From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Anna Schumaker <Anna.Schumaker@Netapp.com>,
Trond Myklebust <trondmy@gmail.com>,
NFS Mailing List <linux-nfs@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the nfs-anna tree
Date: Mon, 7 Feb 2022 07:56:27 +1100 [thread overview]
Message-ID: <20220207075627.1dec35b6@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
Hi all,
In commit
677c0cebca78 ("NFS: Fix initialisation of nfs_client cl_flags field")
Fixes tag
Fixes: 87871d990a2c ("NFSv4: Initialise connection to the server in nfs4_alloc_client()")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: dd99e9f98fbf ("NFSv4: Initialise connection to the server in nfs4_alloc_client()")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-02-06 21:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 20:56 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-12 22:05 linux-next: Fixes tag needs some work in the nfs-anna tree Stephen Rothwell
2022-10-03 21:21 Stephen Rothwell
2020-06-26 23:01 Stephen Rothwell
2020-05-19 18:30 Stephen Rothwell
2019-10-21 20:48 Stephen Rothwell
2019-05-30 21:58 Stephen Rothwell
2019-01-15 21:38 Stephen Rothwell
2019-01-15 21:41 ` Chuck Lever
2019-01-15 22:12 ` Takashi Iwai
2019-01-15 23:38 ` Paul Gortmaker
2019-01-16 6:32 ` Takashi Iwai
2019-01-16 15:24 ` Chuck Lever
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=20220207075627.1dec35b6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Anna.Schumaker@Netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@gmail.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 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).