From: Trond Myklebust <trondmy@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the nfs tree
Date: Fri, 03 Apr 2020 18:22:51 -0400 [thread overview]
Message-ID: <4cd16e845f5709a7ae09809d2d96929901da3b61.camel@gmail.com> (raw)
In-Reply-To: <20200404085512.5ac25c61@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
On Sat, 2020-04-04 at 08:55 +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 52381893a2be ("NFS: Beware when dereferencing the delegation cred")
>
> Fixes tag
>
> Fixes: 5f4adff16fa2 ("NFSv4: nfs_update_inplace_delegation() should
> update delegation cred")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 57f188e04773 ("NFSv4: nfs_update_inplace_delegation() should
> update delegation cred")
>
Doh! The price of juggling too many kernel branches and backports at
the same time. Thanks Stephen!
Cheers
Trond
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-03 22:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 21:55 linux-next: Fixes tag needs some work in the nfs tree Stephen Rothwell
2020-04-03 22:22 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=4cd16e845f5709a7ae09809d2d96929901da3b61.camel@gmail.com \
--to=trondmy@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).