All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Schumaker <bjschuma@netapp.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "Schumaker, Bryan" <Bryan.Schumaker@netapp.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"Isaman, Fred" <Fred.Isaman@netapp.com>
Subject: Re: [PATCH] NFS: Define dummy nfs_init_cinfo() and nfs_init_cinfo_from_inode()
Date: Mon, 30 Apr 2012 14:29:55 -0400	[thread overview]
Message-ID: <4F9EDA23.6080901@netapp.com> (raw)
In-Reply-To: <1335809816.11828.2.camel@lade.trondhjem.org>

On 04/30/2012 02:16 PM, Myklebust, Trond wrote:

> On Mon, 2012-04-30 at 13:48 -0400, bjschuma@netapp.com wrote:
>> From: Bryan Schumaker <bjschuma@netapp.com>
>>
>> These are needed when v3 and v4 are not enabled.
>>
>> Signed-off-by: Bryan Schumaker <bjschuma@netapp.com>
>> ---
>>  fs/nfs/write.c |   12 ++++++++++++
>>  1 file changed, 12 insertions(+)
>>
>> diff --git a/fs/nfs/write.c b/fs/nfs/write.c
>> index 3636191..f0045e0 100644
>> --- a/fs/nfs/write.c
>> +++ b/fs/nfs/write.c
>> @@ -567,6 +567,18 @@ int nfs_write_need_commit(struct nfs_write_data *data)
>>  }
>>  
>>  #else
>> +static void nfs_init_cinfo_from_inode(struct nfs_commit_info *cinfo,
>> +				      struct inode *inode)
>> +{
>> +}
>> +
>> +void nfs_init_cinfo(struct nfs_commit_info *cinfo,
>> +		    struct inode *inode,
>> +		    struct nfs_direct_req *dreq)
>> +{
>> +}
>> +EXPORT_SYMBOL_GPL(nfs_init_cinfo);
>> +
> 
> We shouldn't need to export this. There should be no submodules when
> we're doing NFSv2 only.
> 


Right, I saw a missing symbol error and exported it out of habit.  I'll resend without the export.

- Bryan

      reply	other threads:[~2012-04-30 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-30 17:48 [PATCH] NFS: Define dummy nfs_init_cinfo() and nfs_init_cinfo_from_inode() bjschuma
2012-04-30 18:16 ` Myklebust, Trond
2012-04-30 18:29   ` Bryan Schumaker [this message]

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=4F9EDA23.6080901@netapp.com \
    --to=bjschuma@netapp.com \
    --cc=Bryan.Schumaker@netapp.com \
    --cc=Fred.Isaman@netapp.com \
    --cc=Trond.Myklebust@netapp.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 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.