From: James Bottomley <James.Bottomley@SteelEye.com>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, akpm@osdl.org, jens.axboe@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] FRV: Make BSG declarations dependent on CONFIG_BLOCK
Date: Wed, 01 Aug 2007 08:57:09 -0500 [thread overview]
Message-ID: <1185976630.3468.73.camel@localhost.localdomain> (raw)
In-Reply-To: <20070801091353.10608.32356.stgit@warthog.cambridge.redhat.com>
On Wed, 2007-08-01 at 10:13 +0100, David Howells wrote:
> From: David Howells <dhowells@redhat.com>
>
> Make BSG function declarations dependent on CONFIG_BLOCK as they are not
> compilable if the block layer is compiled out.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
> ---
>
> include/linux/bsg.h | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/bsg.h b/include/linux/bsg.h
> index 102dc09..e917c41 100644
> --- a/include/linux/bsg.h
> +++ b/include/linux/bsg.h
> @@ -47,6 +47,7 @@ struct sg_io_v4 {
> };
>
> #ifdef __KERNEL__
> +#ifdef CONFIG_BLOCK
>
> #if defined(CONFIG_BLK_DEV_BSG)
> struct bsg_class_device {
> @@ -68,6 +69,7 @@ static inline void bsg_unregister_queue(struct request_queue *rq)
> }
> #endif
>
> +#endif /* CONFIG_BLOCK */
> #endif /* __KERNEL__ */
Are you sure you're testing with git head? CONFIG_BLK_DEV_BSG cannot be
set unless CONFIG_BLOCK is (which was a bug in previous releases now
fixed in git head ... unless the fix has gone wrong?).
James
next prev parent reply other threads:[~2007-08-01 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 9:13 [PATCH] FRV: Make BSG declarations dependent on CONFIG_BLOCK David Howells
2007-08-01 13:57 ` James Bottomley [this message]
2007-08-01 14:44 ` David Howells
2007-08-01 17:30 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2007-09-05 15:23 David Howells
2007-09-05 15:56 ` 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=1185976630.3468.73.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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