From: Arnd Bergmann <arnd@arndb.de>
To: Sebastian Siewior <sebastian@breakpoint.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] compat_ioctl requires CONFIG_BLOCK
Date: Sat, 21 Jul 2007 01:08:57 +0200 [thread overview]
Message-ID: <200707210108.58478.arnd@arndb.de> (raw)
In-Reply-To: <20070720225817.050195257@ayoka.breakpoint.cc>
On Saturday 21 July 2007, Sebastian Siewior wrote:
>
> Got with randconfig
> include/linux/loop.h:66: error: expected specifier-qualifier-list before
> 'request_queue_t'
> make[1]: *** [fs/compat_ioctl.o] Error 1
>
> parts of compat ioctl require CONFIG_BLOCK to be set.
>
> Signed-off-by: Sebastian Siewior <sebastian@breakpoint.cc>
> Index: b/fs/compat_ioctl.c
> ===================================================================
> --- a/fs/compat_ioctl.c
> +++ b/fs/compat_ioctl.c
> @@ -63,7 +63,9 @@
> #include <linux/wireless.h>
> #include <linux/atalk.h>
> #include <linux/blktrace_api.h>
> +#ifdef CONFIG_BLOCK
> #include <linux/loop.h>
> +#endif
Adding #ifdef around an #include is considered bad style. Better just
make loop.h compile without any conditionals. Does the below
patch work for you?
Arnd <><
--- a/include/linux/loop.h
+++ b/include/linux/loop.h
@@ -63,7 +63,7 @@ struct loop_device {
struct task_struct *lo_thread;
wait_queue_head_t lo_event;
- request_queue_t *lo_queue;
+ struct request_queue *lo_queue;
struct gendisk *lo_disk;
struct list_head lo_list;
};
next prev parent reply other threads:[~2007-07-20 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 22:58 [PATCH] compat_ioctl requires CONFIG_BLOCK Sebastian Siewior
2007-07-20 23:08 ` Arnd Bergmann [this message]
2007-07-21 8:40 ` Sebastian Siewior
2007-07-21 12:44 ` Christoph Hellwig
2007-07-21 13:17 ` Arnd Bergmann
2007-07-24 0:23 ` Andrew Morton
2007-07-24 6:51 ` Jens Axboe
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=200707210108.58478.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian@breakpoint.cc \
/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.