From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 3/3] Add Doxygen configuration
Date: Thu, 19 Jul 2018 15:44:03 +0200 [thread overview]
Message-ID: <20180719134403.GA24467@rei> (raw)
In-Reply-To: <87k1prbb2n.fsf@rpws.prws.suse.cz>
Hi!
> >> > Not that this is a bad thing quite contrary actually, but it's quite
> >> > confusing that this is a 3/3 of this patchset.
> >> >
> >> > Haven you send this by a mistake?
> >>
> >> Nope, but maybe I should have included a covering letter. I mentioned
> >> that it is not part of the patch set in the notes on the first
> >> commit. I just included it so that you can easily verify the
> >> documentation comments if you want to do that.
> >
> > Ah, I missed that note in the first commit.
> >
> > Hmm, if we decide to go that way we should probably get this in with all
> > the bells and whistles in a separate patchset. I.e. add doxygen target
> > to the doc/Makefile, convert the headers we have and introduce the
> > config.
>
> Are you saying that you want me to submit the patch with the
> documentation in the kernel format, then submit another patch set
> updating all the documentation later?
Actually I do not care that much about the format at this point, as far
as we do not parse it automatically anything human-readable will do...
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-07-19 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 14:56 [LTP] [PATCH v3 1/3] lib: Add tst_crypto and tst_netlink libs Richard Palethorpe
2018-07-05 14:56 ` [LTP] [PATCH v3 2/3] Add pcrypt_aead01 CVE-2017-18075 Richard Palethorpe
2018-07-05 14:56 ` [LTP] [PATCH v3 3/3] Add Doxygen configuration Richard Palethorpe
2018-07-18 12:30 ` Cyril Hrubis
2018-07-18 13:15 ` Richard Palethorpe
2018-07-18 14:54 ` Cyril Hrubis
2018-07-19 13:37 ` Richard Palethorpe
2018-07-19 13:44 ` Cyril Hrubis [this message]
2018-07-19 15:11 ` [LTP] [PATCH v3 1/3] lib: Add tst_crypto and tst_netlink libs Cyril Hrubis
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=20180719134403.GA24467@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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