All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anna Schumaker <bjschuma@netapp.com>
To: Trond Myklebust <trondmy@gmail.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFS: Fix kbuild errors due to missing symbols
Date: Mon, 18 Nov 2013 12:50:24 -0500	[thread overview]
Message-ID: <528A5360.4000206@netapp.com> (raw)
In-Reply-To: <1384557410.3222.2.camel@leira.trondhjem.org>

On 11/15/2013 06:16 PM, Trond Myklebust wrote:
> On Fri, 2013-11-15 at 17:30 -0500, Anna Schumaker wrote:
>> My recent patch 644aa303: "NFS: Enabling v4.2 should not recompile nfsd
>> and lockd" caused build errors when CONFIG_NFS_USE_LEGACY_DNS=y and when
>> CONFIG_NFS_V4=n.  This patch fixes those errors.
>>
> 
> Wait... 
> 
>         config NFS_USE_LEGACY_DNS
>                 bool "Use the legacy NFS DNS resolver"
>                 depends on NFS_V4
>                 help
>                   The kernel now provides a method for translating a host name into an
>                   IP address.  Select Y here if you would rather use your own DNS
>                   resolver script.
>         
>                   If unsure, say N
>         
>         config NFS_USE_KERNEL_DNS
>                 bool
>                 depends on NFS_V4 && !NFS_USE_LEGACY_DNS
>                 select DNS_RESOLVER
>                 default y
> 
> How can that result in NFS_V4=n && NFS_USE_LEGACY_DNS=y?
> 

It's a poorly phrased commit message, actually.  I meant that just setting CONFIG_NFS_USE_LEGACY_DNS=y causes build problems, and then setting CONFIG_NFS_V4=n causes a different set of errors.

  parent reply	other threads:[~2013-11-18 17:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 22:30 [PATCH] NFS: Fix kbuild errors due to missing symbols Anna Schumaker
2013-11-15 23:16 ` Trond Myklebust
2013-11-15 23:25   ` Trond Myklebust
2013-11-18 17:50   ` Anna Schumaker [this message]
2013-11-18 18:37     ` Myklebust, Trond
2013-11-18 18:41       ` Anna Schumaker
2013-11-18 18:48         ` Myklebust, Trond

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=528A5360.4000206@netapp.com \
    --to=bjschuma@netapp.com \
    --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 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.