From: "J. Bruce Fields" <bfields@fieldses.org>
To: George Spelvin <linux@sciencehorizons.net>
Cc: jlayton@poochiereds.net, linux-nfs@vger.kernel.org, linux@horizon.com
Subject: Re: [PATCH RESEND 03/10] <linux/sunrpc/svcauth.h>: Define hash_str() in terms of hash_string()
Date: Fri, 27 May 2016 13:40:19 -0400 [thread overview]
Message-ID: <20160527174019.GE25272@fieldses.org> (raw)
In-Reply-To: <20160527122022.23752.qmail@ns.sciencehorizons.net>
On Fri, May 27, 2016 at 08:20:22AM -0400, George Spelvin wrote:
> > I also needed the following.
>
> I just found out five mintues ago that the push last night failed
> because I forgot the -f. :-( *Now* it'll pull and work.
>
> > But... the resulting kernel isn't booting succesfully for me. Not sure
> > what's up there, I'll investigate some more.
>
> Thank you *so much* for the help, but do get the latest.
I don't see yet what the problem is, but I can tell you that as of
95d5dfa805a6344e69ef41f56bb4955269079ec7 "fs/namei.c: Improve dcache
hash function" my (Fedora 21 x86_64) VM no longer starts up reliably....
--b.
next prev parent reply other threads:[~2016-05-27 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160527003254.GA25272@fieldses.org>
2016-05-27 1:56 ` [PATCH RESEND 03/10] <linux/sunrpc/svcauth.h>: Define hash_str() in terms of hash_string() George Spelvin
2016-05-27 3:29 ` George Spelvin
2016-05-27 12:16 ` J. Bruce Fields
2016-05-27 12:20 ` George Spelvin
2016-05-27 17:40 ` J. Bruce Fields [this message]
2016-05-27 21:25 ` George Spelvin
2016-05-27 17:14 ` I may be on the trail of that bug you hit George Spelvin
2016-05-25 7:26 [PATCH 03/10] <linux/sunrpc/svcauth.h>: Define hash_str() in terms of hash_string() George Spelvin
2016-05-26 18:39 ` [PATCH RESEND " George Spelvin
2016-05-26 18:45 ` J. Bruce Fields
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=20160527174019.GE25272@fieldses.org \
--to=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-nfs@vger.kernel.org \
--cc=linux@horizon.com \
--cc=linux@sciencehorizons.net \
/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.