All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rlandley@parallels.com>
To: Mi Jinlong <mijinlong@cn.fujitsu.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: Re: What's nlmsvc_proc_share() for?
Date: Thu, 7 Apr 2011 20:09:55 -0500	[thread overview]
Message-ID: <4D9E6063.1020607@parallels.com> (raw)
In-Reply-To: <4D9D29A5.7000507@cn.fujitsu.com>

On 04/06/2011 10:04 PM, Mi Jinlong wrote:
> Rob Landley:
>> What's this code for, and where does it get used?  Is it something out
>> of tree, or some header #define that's glued##together that I'm not
>> picking up via grep...?
> 
>   Maybe you can get some info from the following code at fs/lockd/svc4proc.c:
> 
>  462 
>  463 #define PROC(name, xargt, xrest, argt, rest, respsize)  \
>  464  { .pc_func     = (svc_procfunc) nlm4svc_proc_##name,   \
...
>  498   PROC(share,           shareargs,      shareres,       args,   res, Ck+St+1),

So it's glued##together in a macro.  Got it.

Thanks,

Rob

      reply	other threads:[~2011-04-08  1:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 14:30 What's nlmsvc_proc_share() for? Rob Landley
2011-04-07  3:04 ` Mi Jinlong
2011-04-08  1:09   ` Rob Landley [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=4D9E6063.1020607@parallels.com \
    --to=rlandley@parallels.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mijinlong@cn.fujitsu.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.