mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Geliang Tang <geliangtang@163.com>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	Jeff Layton <jlayton@poochiereds.net>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] lockd: use to_delayed_work
Date: Mon, 4 Jan 2016 17:44:11 -0500	[thread overview]
Message-ID: <20160104224411.GF30315@fieldses.org> (raw)
In-Reply-To: <741bd37af1f46a3713423e16138910f12a5c12b5.1451656900.git.geliangtang@163.com>

On Fri, Jan 01, 2016 at 10:06:29PM +0800, Geliang Tang wrote:
> Use to_delayed_work() instead of open-coding it.

Thanks, applying 2/3 and 3/3 for 4.5.--b.

> 
> Signed-off-by: Geliang Tang <geliangtang@163.com>
> ---
>  fs/lockd/svc.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/fs/lockd/svc.c b/fs/lockd/svc.c
> index 44d18ad..b4006c72 100644
> --- a/fs/lockd/svc.c
> +++ b/fs/lockd/svc.c
> @@ -94,8 +94,7 @@ static unsigned long get_lockd_grace_period(void)
>  
>  static void grace_ender(struct work_struct *grace)
>  {
> -	struct delayed_work *dwork = container_of(grace, struct delayed_work,
> -						  work);
> +	struct delayed_work *dwork = to_delayed_work(grace);
>  	struct lockd_net *ln = container_of(dwork, struct lockd_net,
>  					    grace_period_end);
>  
> -- 
> 2.5.0
> 

  reply	other threads:[~2016-01-04 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01 14:06 [PATCH 1/3] jffs2: " Geliang Tang
2016-01-01 14:06 ` [PATCH 2/3] nfsd: " Geliang Tang
2016-01-01 14:06 ` [PATCH 3/3] lockd: " Geliang Tang
2016-01-04 22:44   ` J. Bruce Fields [this message]
2016-01-06 23:17 ` [PATCH 1/3] jffs2: " Brian Norris

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=20160104224411.GF30315@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=anna.schumaker@netapp.com \
    --cc=geliangtang@163.com \
    --cc=jlayton@poochiereds.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome