From: Johannes Berg <johannes@sipsolutions.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Arend van Spriel <arend@broadcom.com>,
george@znau.edu.ua, zajec5@gmail.com, mb@bu3sch.de,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [RFC] drivers: brcmaxi: provide amba axi functionality in separate module
Date: Mon, 21 Mar 2011 21:45:44 +0100 [thread overview]
Message-ID: <1300740344.13397.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20110321134223.43791d78.rdunlap@xenotime.net>
On Mon, 2011-03-21 at 13:42 -0700, Randy Dunlap wrote:
> On Mon, 21 Mar 2011 21:38:12 +0100 Johannes Berg wrote:
>
> > On Mon, 2011-03-21 at 13:28 -0700, Randy Dunlap wrote:
> >
> > > > +/**
> > > > + * DOC: Core Utility Functions
> >
> > > This is not kernel-doc notation. Change /** to /*.
> >
> > Actually, it is, if you prefix with DOC: you can embed that into the
> > generated DocBook with
> > !P<file> <heading name>
> > and include the text. I did that in b112e0f7 :-)
>
> Yes, I'm familiar with that notation.
>
>
> bah. You omitted a few lines of comments:
>
> > +/**
>
> This is not kernel-doc notation. Change /** to /*.
Oops, I just looked at the original again and noticed that in fact you
were commenting on a new block that started. You're right, of course,
sorry!
johannes
next prev parent reply other threads:[~2011-03-21 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 20:16 [RFC] drivers: brcmaxi: AMBA AXI functionality library module Arend van Spriel
2011-03-21 20:16 ` [RFC] drivers: brcmaxi: provide amba axi functionality in separate module Arend van Spriel
2011-03-21 20:28 ` Randy Dunlap
2011-03-21 20:38 ` Johannes Berg
2011-03-21 20:42 ` Randy Dunlap
2011-03-21 20:45 ` Johannes Berg [this message]
2011-03-23 10:51 ` Arend van Spriel
[not found] ` <1300888183.18815.5.camel@Nokia-N900>
2011-03-23 13:54 ` Arend van Spriel
2011-03-23 14:09 ` Michael Büsch
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=1300740344.13397.6.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=george@znau.edu.ua \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=rdunlap@xenotime.net \
--cc=zajec5@gmail.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 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.