From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Sven Eckelmann <sven@narfation.org>,
David Ahern <dsahern@gmail.com>
Subject: [B.A.T.M.A.N.] [PATCH 3/3] batman-adv: Add missing kerneldoc for extack
Date: Sat, 7 Oct 2017 14:21:22 +0200 [thread overview]
Message-ID: <20171007122122.6470-1-sven@narfation.org> (raw)
In-Reply-To: <20171007121853.6278-1-sven@narfation.org>
The parameter extack was added to batadv_softif_slave_add without adding
the kernel-doc for it. This caused kernel-doc warnings.
Signed-off-by: Sven Eckelmann <sven@narfation.org>
Cc: David Ahern <dsahern@gmail.com>
---
net/batman-adv/soft-interface.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/batman-adv/soft-interface.c b/net/batman-adv/soft-interface.c
index 543d2c3e..9f673cdf 100644
--- a/net/batman-adv/soft-interface.c
+++ b/net/batman-adv/soft-interface.c
@@ -863,6 +863,7 @@ static int batadv_softif_init_late(struct net_device *dev)
* batadv_softif_slave_add - Add a slave interface to a batadv_soft_interface
* @dev: batadv_soft_interface used as master interface
* @slave_dev: net_device which should become the slave interface
+ * @extack: extended ACK report struct
*
* Return: 0 if successful or error otherwise.
*/
--
2.11.0
next prev parent reply other threads:[~2017-10-07 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 12:18 [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: Add extack to ndo_add_slave Sven Eckelmann
2017-10-07 12:18 ` [B.A.T.M.A.N.] [PATCH 2/3] batman-adv: Add extack to upper device linking Sven Eckelmann
2017-10-07 12:21 ` Sven Eckelmann [this message]
2017-10-07 14:23 ` [B.A.T.M.A.N.] [PATCH 3/3] batman-adv: Add missing kerneldoc for extack David Ahern
2017-10-07 19:59 ` David Miller
2017-10-08 7:29 ` Sven Eckelmann
2017-10-08 17:04 ` David Miller
2017-10-16 17:07 ` [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: Add extack to ndo_add_slave Sven Eckelmann
2017-10-16 17:12 ` Sven Eckelmann
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=20171007122122.6470-1-sven@narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=netdev@vger.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: 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).