LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Alan Tull <atull@kernel.org> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Jonathan Corbet <corbet@lwn.net>, Moritz Fischer <mdf@kernel.org> Cc: linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org, Alan Tull <atull@kernel.org> Subject: [PATCH 07/14] fpga: bridge: kernel-doc fixes Date: Wed, 16 May 2018 18:50:00 -0500 [thread overview] Message-ID: <20180516235007.3951-8-atull@kernel.org> (raw) In-Reply-To: <20180516235007.3951-1-atull@kernel.org> Fix the following warnings when documentation is built: ./drivers/fpga/fpga-bridge.c:143: warning: Function parameter or member 'info' not described in 'fpga_bridge_get' ./drivers/fpga/fpga-bridge.c:1: warning: no structured comments found Signed-off-by: Alan Tull <atull@kernel.org> --- drivers/fpga/fpga-bridge.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/fpga/fpga-bridge.c b/drivers/fpga/fpga-bridge.c index 164eb55..4b207a7 100644 --- a/drivers/fpga/fpga-bridge.c +++ b/drivers/fpga/fpga-bridge.c @@ -121,6 +121,7 @@ static int fpga_bridge_dev_match(struct device *dev, const void *data) /** * fpga_bridge_get - get an exclusive reference to a fpga bridge * @dev: parent device that fpga bridge was registered with + * @info: fpga manager info * * Given a device, get an exclusive reference to a fpga bridge. * -- 2.7.4
next prev parent reply other threads:[~2018-05-16 23:52 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-16 23:49 [PATCH 00/14] fpga api changes and kernel-doc fixup Alan Tull 2018-05-16 23:49 ` [PATCH 01/14] fpga: region: don't use drvdata in common fpga code Alan Tull 2018-05-16 23:49 ` [PATCH 02/14] fpga: manager: change api, don't use drvdata Alan Tull 2018-05-16 23:49 ` [PATCH 03/14] fpga: bridge: " Alan Tull 2018-05-16 23:49 ` [PATCH 04/14] fpga: region: change api, add fpga_region_create/free Alan Tull 2018-05-16 23:49 ` [PATCH 05/14] fpga: use SPDX Alan Tull 2018-05-16 23:49 ` [PATCH 06/14] fpga: mgr: kernel-doc fixes Alan Tull 2018-05-24 17:07 ` Moritz Fischer 2018-05-16 23:50 ` Alan Tull [this message] 2018-05-24 17:08 ` [PATCH 07/14] fpga: bridge: " Moritz Fischer 2018-05-16 23:50 ` [PATCH 08/14] fpga: region: " Alan Tull 2018-05-24 17:09 ` Moritz Fischer 2018-05-16 23:50 ` [PATCH 09/14] Documentation: fpga: move fpga overview to driver-api Alan Tull 2018-05-26 2:21 ` Randy Dunlap 2018-05-16 23:50 ` [PATCH 10/14] documentation: fpga: move fpga-mgr.txt " Alan Tull 2018-05-26 2:29 ` Randy Dunlap 2018-05-16 23:50 ` [PATCH 11/14] documentation: fpga: add bridge document " Alan Tull 2018-05-16 23:50 ` [PATCH 12/14] documentation: fpga: move fpga-region.txt " Alan Tull 2018-05-26 2:33 ` Randy Dunlap 2018-05-29 16:15 ` Alan Tull 2018-05-16 23:50 ` [PATCH 13/14] fpga: clarify that unregister functions also free Alan Tull 2018-05-16 23:50 ` [PATCH 14/14] MAINTAINERS: Add driver-api/fpga path Alan Tull 2018-05-17 7:04 ` [PATCH 00/14] fpga api changes and kernel-doc fixup Greg Kroah-Hartman 2018-05-17 14:08 ` Alan Tull
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=20180516235007.3951-8-atull@kernel.org \ --to=atull@kernel.org \ --cc=corbet@lwn.net \ --cc=gregkh@linuxfoundation.org \ --cc=linux-fpga@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mdf@kernel.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: linkBe 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).