All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	linux-nfs@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Scott Mayhew <smayhew@redhat.com>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [BISECT BUG] NFS v4 root not working after 6d972518b821 ("NFS: Add fs_context support.")
Date: Fri, 17 Jan 2020 15:36:28 +0100	[thread overview]
Message-ID: <20200117143628.GA3215@pi3> (raw)
In-Reply-To: <432921.1579270135@warthog.procyon.org.uk>

On Fri, Jan 17, 2020 at 02:08:55PM +0000, David Howells wrote:
> Can you do:
> 
> 	grep NFS .config
> 
> for your kernel config?

It is a regular exynos_defconfig from the same tree (so linux-next).

Best regards,
Krzysztof


  reply	other threads:[~2020-01-17 14:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 11:33 [BISECT BUG] NFS v4 root not working after 6d972518b821 ("NFS: Add fs_context support.") Krzysztof Kozlowski
2020-01-17  0:49 ` Scott Mayhew
2020-01-17 11:53   ` Krzysztof Kozlowski
2020-01-17 12:54 ` David Howells
2020-01-17 13:16   ` Krzysztof Kozlowski
2020-01-17 14:08   ` David Howells
2020-01-17 14:36     ` Krzysztof Kozlowski [this message]
2020-01-17 14:20 ` David Howells
2020-01-17 14:40   ` Krzysztof Kozlowski
2020-01-17 15:12   ` David Howells
2020-01-17 15:17     ` Trond Myklebust
2020-01-17 15:32       ` Scott Mayhew
2020-01-17 15:44     ` David Howells
2020-01-17 15:48   ` [PATCH] nfs: Return EINVAL rather than ERANGE for mount parse errors David Howells
2020-01-17 15:55   ` [PATCH v2] " David Howells
2020-01-17 16:51     ` Krzysztof Kozlowski
2020-01-17 17:18     ` David Howells
2020-01-17 20:21       ` Schumaker, Anna
2020-01-17 21:12       ` David Howells

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=20200117143628.GA3215@pi3 \
    --to=krzk@kernel.org \
    --cc=anna.schumaker@netapp.com \
    --cc=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=smayhew@redhat.com \
    --cc=trond.myklebust@hammerspace.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.