mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
	akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH -mmotm] nfs/cache_lib: fix sunrpc struct build error
Date: Fri, 21 Aug 2009 13:51:12 -0400	[thread overview]
Message-ID: <1250877072.27154.10.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20090821095756.390c102e.randy.dunlap@oracle.com>

On Fri, 2009-08-21 at 09:57 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Add header file for struct delayed_work:
> 
> In file included from fs/nfs/cache_lib.c:14:
> include/linux/sunrpc/rpc_pipe_fs.h:35: error: field 'queue_timeout' has incomplete type
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>  include/linux/sunrpc/rpc_pipe_fs.h |    2 ++
>  1 file changed, 2 insertions(+)
> 
> --- mmotm-2009-0820-1918.orig/include/linux/sunrpc/rpc_pipe_fs.h
> +++ mmotm-2009-0820-1918/include/linux/sunrpc/rpc_pipe_fs.h
> @@ -3,6 +3,8 @@
>  
>  #ifdef __KERNEL__
>  
> +#include <linux/workqueue.h>
> +
>  struct rpc_pipe_msg {
>  	struct list_head list;
>  	void *data;

Thanks Randy! Bruce Fields beat you to this bug by a few hours, so I've
already applied his fix. It should hit linux-next et al today.

Cheers
  Trond

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com

  reply	other threads:[~2009-08-21 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21  2:22 mmotm 2009-08-20-19-18 uploaded akpm
2009-08-21 10:38 ` Dave Young
2009-08-21 18:43   ` Balbir Singh
2009-08-21 20:50   ` Paul Menage
2009-08-21 16:57 ` [PATCH -mmotm] nfs/cache_lib: fix sunrpc struct build error Randy Dunlap
2009-08-21 17:51   ` Trond Myklebust [this message]
2009-08-21 16:58 ` [PATCH -mmotm] ummunotify: fix userspace build Randy Dunlap
2009-08-21 17:44   ` Roland Dreier

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=1250877072.27154.10.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=randy.dunlap@oracle.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

all inboxes | Powered by JetHome®