From: Omar Sandoval <osandov@osandov.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Jens Axboe <axboe@kernel.dk>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>,
linux-scsi@vger.kernel.org,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
Omar Sandoval <osandov@fb.com>, Ming Lei <ming.lei@redhat.com>,
Paolo Valente <paolo.valente@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [v2] sbitmap, scsi/target: add seq_file forward declaration
Date: Fri, 6 Jul 2018 13:58:00 -0700 [thread overview]
Message-ID: <20180706205800.GD25954@vader> (raw)
In-Reply-To: <20180706201920.2185565-1-arnd@arndb.de>
On Fri, Jul 06, 2018 at 10:19:07PM +0200, Arnd Bergmann wrote:
> The target core runs into a warning in the linux/sbitmap.h
> file in some configurations:
>
> In file included from include/target/target_core_base.h:7,
> from drivers/target/target_core_fabric_lib.c:41:
> include/linux/sbitmap.h:331:46: error: 'struct seq_file' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
> void sbitmap_show(struct sbitmap *sb, struct seq_file *m);
> ^~~~~~~~
>
> In general, headers should not depend on others being included first,
> so this fixes it with a forward declaration for that struct name, but
> we probably want to merge the patch through the scsi tree to help
> bisection.
>
> Fixes: 10e9cbb6b531 ("scsi: target: Convert target drivers to use sbitmap")
Reviewed-by: Omar Sandoval <osandov@fb.com>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> v2: move declaration to the start of the header, as suggested by Bart
> ---
> include/linux/sbitmap.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/sbitmap.h b/include/linux/sbitmap.h
> index e6539536dea9..804a50983ec5 100644
> --- a/include/linux/sbitmap.h
> +++ b/include/linux/sbitmap.h
> @@ -23,6 +23,8 @@
> #include <linux/kernel.h>
> #include <linux/slab.h>
>
> +struct seq_file;
> +
> /**
> * struct sbitmap_word - Word in a &struct sbitmap.
> */
> --
> 2.9.0
>
next prev parent reply other threads:[~2018-07-06 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 20:19 [PATCH] [v2] sbitmap, scsi/target: add seq_file forward declaration Arnd Bergmann
2018-07-06 20:33 ` Bart Van Assche
2018-07-06 20:58 ` Omar Sandoval [this message]
2018-07-11 2:54 ` Martin K. Petersen
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=20180706205800.GD25954@vader \
--to=osandov@osandov.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=felipe.balbi@linux.intel.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=paolo.valente@linaro.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).