From: atull <atull@opensource.altera.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: gregkh@linuxfoundation.org, jgunthorpe@obsidianresearch.com,
hpa@zytor.com, monstr@monstr.eu, rdunlap@infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
pantelis.antoniou@konsulko.com, robh+dt@kernel.org,
grant.likely@linaro.org, iws@ovro.caltech.edu,
linux-doc@vger.kernel.org, pavel@denx.de, broonie@kernel.org,
philip@balister.org, rubini@gnudd.com, s.trumtrar@pengutronix.de,
jason@lakedaemon.net, kyle.teske@ni.com, nico@linaro.org,
balbi@ti.com, m.chehab@samsung.com, davidb@codeaurora.org,
rob@landley.net, davem@davemloft.net, cesarb@cesarb.net,
sameo@linux.intel.com, akpm@linux-foundation.org,
linus.walleij@linaro.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, devel@driverdev.osuosl.org,
delicious.quinoa@gmail.com, dinguye
Subject: Re: [PATCH v5 3/6] staging: fpga manager: framework core
Date: Thu, 18 Dec 2014 14:46:15 -0600 [thread overview]
Message-ID: <alpine.DEB.2.02.1412181440490.25208@linuxheads99> (raw)
In-Reply-To: <05395a89d783481b8b7c06bb299b53e0@BL2FFO11FD020.protection.gbl>
On Thu, 18 Dec 2014, Michal Simek wrote:
> Hi Alan,
>
> first of all - there are these kernel-doc warnings.
>
> Info(drivers/staging/fpga/fpga-mgr.c:37): Scanning doc for fpga_mgr_low_level_state
> Warning(drivers/staging/fpga/fpga-mgr.c:43): No description found for return value of 'fpga_mgr_low_level_state'
> Info(drivers/staging/fpga/fpga-mgr.c:51): Scanning doc for __fpga_mgr_reset
> Warning(drivers/staging/fpga/fpga-mgr.c:55): No description found for return value of '__fpga_mgr_reset'
> Info(drivers/staging/fpga/fpga-mgr.c:69): Scanning doc for fpga_mgr_reset
> Warning(drivers/staging/fpga/fpga-mgr.c:73): No description found for return value of 'fpga_mgr_reset'
> Info(drivers/staging/fpga/fpga-mgr.c:88): Scanning doc for __fpga_mgr_stage_init
> Warning(drivers/staging/fpga/fpga-mgr.c:92): No description found for return value of '__fpga_mgr_stage_write_init'
> Info(drivers/staging/fpga/fpga-mgr.c:108): Scanning doc for __fpga_mgr_stage_write
> Warning(drivers/staging/fpga/fpga-mgr.c:115): No description found for return value of '__fpga_mgr_stage_write'
> Info(drivers/staging/fpga/fpga-mgr.c:129): Scanning doc for __fpga_mgr_stage_complete
> Warning(drivers/staging/fpga/fpga-mgr.c:133): No description found for return value of '__fpga_mgr_stage_write_complete'
> Info(drivers/staging/fpga/fpga-mgr.c:151): Scanning doc for __fpga_mgr_write
> Warning(drivers/staging/fpga/fpga-mgr.c:158): No description found for return value of '__fpga_mgr_write'
> Info(drivers/staging/fpga/fpga-mgr.c:173): Scanning doc for fpga_mgr_write
> Warning(drivers/staging/fpga/fpga-mgr.c:179): No description found for return value of 'fpga_mgr_write'
> Info(drivers/staging/fpga/fpga-mgr.c:195): Scanning doc for fpga_mgr_firmware_write
> Warning(drivers/staging/fpga/fpga-mgr.c:204): No description found for return value of 'fpga_mgr_firmware_write'
> Info(drivers/staging/fpga/fpga-mgr.c:234): Scanning doc for fpga_mgr_name
> Warning(drivers/staging/fpga/fpga-mgr.c:239): No description found for return value of 'fpga_mgr_name'
> Info(drivers/staging/fpga/fpga-mgr.c:414): Scanning doc for fpga_mgr_register
> Warning(drivers/staging/fpga/fpga-mgr.c:423): No description found for return value of 'fpga_mgr_register'
> Info(drivers/staging/fpga/fpga-mgr.c:480): Scanning doc for fpga_mgr_remove
> Warning(drivers/staging/fpga/fpga-mgr.c:484): No description found for parameter 'pdev'
> Warning(drivers/staging/fpga/fpga-mgr.c:484): Excess function parameter 'dev' description in 'fpga_mgr_remove'
>
I see the warnings now. I wasn't using the '-v' option for kernel-doc.
Fixed in v6.
> > diff --git a/drivers/staging/fpga/Makefile b/drivers/staging/fpga/Makefile
> > new file mode 100644
> > index 0000000..ff6c677
> > --- /dev/null
> > +++ b/drivers/staging/fpga/Makefile
> > @@ -0,0 +1,10 @@
> > +#
> > +# Makefile for the fpga framework and fpga manager drivers.
> > +#
> > +
> > +fpga-mgr-core-y += fpga-mgr.o
>
> remove this line - it is unused.
>
OK
> > +static int __init fpga_mgr_dev_init(void)
> > +{
> > + pr_info("FPGA Manager framework driver\n");
> > +
> > + fpga_mgr_class = class_create(THIS_MODULE, "fpga_manager");
> > + if (IS_ERR(fpga_mgr_class))
> > + return PTR_ERR(fpga_mgr_class);
> > +
> > + fpga_mgr_class->dev_groups = fpga_mgr_groups;
>
>
> Write this here.
> if (IS_ENABLED(CONFIG_FPGA_MGR_SYSFS)) {
> fpga_mgr_class->dev_groups = fpga_mgr_groups;
> }
>
> I have tested it and it is working just fine. You can compile this
> driver with SYSFS=n
> The whole code is built and config option just export it.
> I think it is better than having #if there.
>
> Greg: Is there any problem with this solution?
>
I'm cool with this myself. I'll add in v6.
> BTW: I have pushed my branch to zero day testing system to get better coverage
>
Michal, I've already done that with each submission. Assuming you are
referring to the kbuild test robot.
Alan
> Thanks,
> Michal
>
>
>
next prev parent reply other threads:[~2014-12-18 20:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 16:54 [PATCH v5 0/6] FPGA Manager Framework atull
2014-12-17 16:54 ` [PATCH v5 2/6] fpga manager: add sysfs interface document atull
[not found] ` <1418835289-15752-1-git-send-email-atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2014-12-17 16:54 ` [PATCH v5 1/6] doc: add bindings document for altera fpga manager atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx
2014-12-17 16:54 ` [PATCH v5 3/6] staging: fpga manager: framework core atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx
2014-12-18 18:16 ` Michal Simek
2014-12-18 20:46 ` atull [this message]
2014-12-19 7:22 ` Michal Simek
2014-12-17 16:54 ` [PATCH v5 4/6] staging: fpga manager: add driver for socfpga fpga manager atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx
2014-12-18 15:31 ` Michal Simek
2014-12-18 20:59 ` atull
2014-12-19 7:30 ` Michal Simek
2014-12-17 16:54 ` [PATCH v5 5/6] arm: dts: socfpga: add altera " atull
2014-12-17 16:54 ` [PATCH v5 6/6] ARM: socfpga: defconfig: enable " atull
2014-12-17 17:32 ` Greg KH
[not found] ` <20141217173216.GA24913-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2014-12-17 18:33 ` Michal Simek
2014-12-17 19:41 ` atull
2014-12-17 18:46 ` Jason Cooper
2014-12-17 22:00 ` Pavel Machek
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=alpine.DEB.2.02.1412181440490.25208@linuxheads99 \
--to=atull@opensource.altera.com \
--cc=akpm@linux-foundation.org \
--cc=balbi@ti.com \
--cc=broonie@kernel.org \
--cc=cesarb@cesarb.net \
--cc=davem@davemloft.net \
--cc=davidb@codeaurora.org \
--cc=delicious.quinoa@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=iws@ovro.caltech.edu \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=kyle.teske@ni.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=nico@linaro.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=pavel@denx.de \
--cc=pawel.moll@arm.com \
--cc=philip@balister.org \
--cc=rdunlap@infradead.org \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=rubini@gnudd.com \
--cc=s.trumtrar@pengutronix.de \
--cc=sameo@linux.intel.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