From: Johannes Berg <johannes@sipsolutions.net>
To: Jani Nikula <jani.nikula@intel.com>, linux-wireless@vger.kernel.org
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: use inline kernel-doc for struct ieee80211_hw
Date: Wed, 26 Oct 2016 10:55:04 +0200 [thread overview]
Message-ID: <1477472104.4059.21.camel@sipsolutions.net> (raw)
In-Reply-To: <87bmy7mrq1.fsf@intel.com>
On Wed, 2016-10-26 at 11:36 +0300, Jani Nikula wrote:
> On Wed, 26 Oct 2016, Johannes Berg <johannes@sipsolutions.net> wrote:
> >
> > On Fri, 2016-10-21 at 15:57 +0300, Jani Nikula wrote:
> > >
> > > It's easier to manage the kernel-doc for the fields when they
> > > documentation is next to the field.
> >
> > Ok, actually, this doesn't apply. Perhaps I'll look into scripting
> > this
> > kind of conversion.
>
> No problem; I'll leave it up to you.
I'll probably end up doing it manually though - no chance I can extend
the parser to output an spatch (doing the comment placement with spatch
actually works, but getting there...)
next prev parent reply other threads:[~2016-10-26 8:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 12:57 [PATCH 1/2] mac80211: fix some sphinx warnings Jani Nikula
2016-10-21 12:57 ` [PATCH 2/2] mac80211: use inline kernel-doc for struct ieee80211_hw Jani Nikula
2016-10-21 13:01 ` Johannes Berg
2016-10-21 13:18 ` Jani Nikula
2016-10-21 18:59 ` Arend van Spriel
2016-10-21 19:56 ` Johannes Berg
2016-10-26 6:09 ` Johannes Berg
2016-10-26 8:36 ` Jani Nikula
2016-10-26 8:55 ` Johannes Berg [this message]
2016-10-21 13:01 ` [PATCH 1/2] mac80211: fix some sphinx warnings Johannes Berg
2016-10-21 13:14 ` Jani Nikula
2016-10-21 13:17 ` Johannes Berg
2016-10-26 6:02 ` Johannes Berg
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=1477472104.4059.21.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-wireless@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).