From: Trond Myklebust <trondmy@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@lst.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the nfs tree
Date: Mon, 14 Jul 2025 15:30:11 -0700 [thread overview]
Message-ID: <6af3f3273703c29dad890934a7fdb14153858ff8.camel@gmail.com> (raw)
In-Reply-To: <20250715075731.52b7485e@canb.auug.org.au>
On Tue, 2025-07-15 at 07:57 +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> dad2fe3c563d ("NFS: drop __exit from nfs_exit_keyring")
>
> Fixes tag
>
> Fixes: 2c285621176c ("nfs: create a kernel keyring")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 6a247819238d ("nfs: create a kernel keyring")
Thanks! Fixed, and ditto with the other one.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trondmy@kernel.org, trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2025-07-14 22:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 21:57 linux-next: Fixes tag needs some work in the nfs tree Stephen Rothwell
2025-07-14 22:30 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-04 7:36 Stephen Rothwell
2025-12-04 14:29 ` Trond Myklebust
2025-07-14 21:54 Stephen Rothwell
2024-03-07 22:28 Stephen Rothwell
2022-12-15 0:54 Stephen Rothwell
2022-12-15 23:18 ` Trond Myklebust
2021-06-03 22:20 Stephen Rothwell
2021-01-10 2:14 Stephen Rothwell
2021-01-10 17:13 ` Trond Myklebust
2020-12-14 10:38 Stephen Rothwell
2020-08-04 22:10 Stephen Rothwell
2020-05-14 22:33 Stephen Rothwell
2020-04-21 22:05 Stephen Rothwell
2020-04-03 21:55 Stephen Rothwell
2020-04-03 22:22 ` Trond Myklebust
2019-11-19 20:47 Stephen Rothwell
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=6af3f3273703c29dad890934a7fdb14153858ff8.camel@gmail.com \
--to=trondmy@gmail.com \
--cc=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox