From: Johannes Berg <johannes@sipsolutions.net>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: linux-wireless@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] mac80211: fix documentation warnings
Date: Fri, 13 Jan 2017 14:14:23 +0100 [thread overview]
Message-ID: <1484313263.8670.1.camel@sipsolutions.net> (raw)
In-Reply-To: <4973EEB8-5F54-451E-B939-CDA94332CEF7@darmarit.de>
On Fri, 2017-01-13 at 13:43 +0100, Markus Heiser wrote:
> does it make live easier when we use in-line member comments:
>
> https://www.kernel.org/doc/html/latest/doc-guide/kernel-doc.html#in-
> line-member-documentation-comments
>
> and place the entire list in a literalblock?
Ah yes, I forgot about that. I should convert everything to that, but
that's probably better done separately.
johannes
prev parent reply other threads:[~2017-01-13 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 10:12 [PATCH] mac80211: fix documentation warnings Johannes Berg
2017-01-13 12:43 ` Markus Heiser
2017-01-13 13:14 ` Johannes Berg [this message]
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=1484313263.8670.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.