All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shirley Ma <shirley.ma@oracle.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Jeff Layton <jlayton@primarydata.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [RFC PATCH V3 1/7] nfsd/sunrpc: add a new svc_serv_ops struct and move sv_shutdown into it
Date: Mon, 08 Jun 2015 08:55:27 -0700	[thread overview]
Message-ID: <5575BAEF.4080704@oracle.com> (raw)
In-Reply-To: <CAHQdGtQ6NSf2o+Tn=8f0HzECFV3WUOKcPODY-+-RmafUu6Mt7w@mail.gmail.com>



On 06/08/2015 05:42 AM, Trond Myklebust wrote:
> On Mon, Jun 8, 2015 at 1:21 AM, Shirley Ma <shirley.ma@oracle.com> wrote:
>> sunrpc: add a new svc_serv_ops struct and move sv_shutdown into it
> 
> The subject does not need to be duplicated in the body of the email.
> 
>> In later patches we'll need to abstract out more operations on a
>> per-service level, besides sv_shutdown and sv_function.
>>
>> Declare a new svc_serv_ops struct to hold these operations, and move
>> sv_shutdown into this struct.
>>
>> Author: Jeff Layton <jlayton@primarydata.com>
> 
> This should read
> 
> From: Jeff Layton <jlayton@primarydata.com>
> 
> and should be the first line in the body of your email so that 'git'
> can pick it up automatically. See Documentation/SubmittingPatches

Thanks, I will modify and resend these patches.

> Trond
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2015-06-08 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 12:42 [RFC PATCH V3 1/7] nfsd/sunrpc: add a new svc_serv_ops struct and move sv_shutdown into it Trond Myklebust
2015-06-08 15:55 ` Shirley Ma [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-08  5:21 Shirley Ma

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=5575BAEF.4080704@oracle.com \
    --to=shirley.ma@oracle.com \
    --cc=bfields@fieldses.org \
    --cc=jlayton@primarydata.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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.