public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH]  Fixed compile errors when the mount config file is not enabled
Date: Mon, 16 Nov 2009 13:28:54 -0500	[thread overview]
Message-ID: <4B0199E6.20405@RedHat.com> (raw)
In-Reply-To: <36FDE8D9-4D83-447F-A2AF-516B5FEFDAD7@oracle.com>



On 10/27/2009 04:20 PM, Chuck Lever wrote:
> Hi-
> 
> On Oct 27, 2009, at 4:02 PM, Steve Dickson wrote:
> 
>> Author: Steve Dickson <steved@redhat.com>
>> Date:   Tue Oct 27 15:47:27 2009 -0400
>>
>>    Added wrappers around the setting of default values
>>    from the config file which will be compiled out
>>    when the config file is not enabled.
>>
>>    Signed-off-by: Steve Dickson <steved@redhat.com>
>>
>> diff --git a/support/include/conffile.h b/support/include/conffile.h
>> index fe23ec2..ce7aa21 100644
>> --- a/support/include/conffile.h
>> +++ b/support/include/conffile.h
>> @@ -76,10 +76,5 @@ static inline void upper2lower(char *str)
>>         *str++ = c;
>> }
>>
>> -/*
>> - * Default Mount options
>> - */
>> -extern unsigned long config_default_vers;
>> -extern unsigned long config_default_proto;
>>
>> #endif                /* _CONFFILE_H_ */
>> diff --git a/utils/mount/network.c b/utils/mount/network.c
>> index e651167..d4ecbc9 100644
>> --- a/utils/mount/network.c
>> +++ b/utils/mount/network.c
>> @@ -172,6 +172,27 @@ static const unsigned long probe_mnt3_first[] = {
>>     0,
>> };
>>
>> +inline const unsigned int *set_default_proto(void);
> 
> The "inline" directives are visual clutter, really... shouldn't this be
> "static" instead (which in most normal cases implies "inline")? 
> Otherwise, you also clutter up the linker's symbol name space with these
> generic function names.  I've been prefixing function names with "nfs_"
> for most global functions, to make debugging easier.
I made these changes a while ago... I guess I forgot to mention 
it... thanks of the input!

steved.

  parent reply	other threads:[~2009-11-16 18:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 20:02 [PATCH] Fixed compile errors when the mount config file is not enabled Steve Dickson
     [not found] ` <4AE751CE.1050300-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-10-27 20:20   ` Chuck Lever
2009-11-03 15:23     ` Steve Dickson
2009-11-16 18:28     ` Steve Dickson [this message]
2009-10-28 12:20   ` Peter Staubach
2009-11-03 14:54     ` Steve Dickson

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=4B0199E6.20405@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    /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