ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	"ksummit-discuss\@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Cc: Grant Likely <grant.likely@linaro.org>,
	Markus Heiser <markus.heiser@darmarit.de>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] kernel documentation
Date: Tue, 02 Aug 2016 17:34:55 +0300	[thread overview]
Message-ID: <87y44fqlww.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uHOmxoRFr2j+KrtVAud1iQq3ySDQMz6rZOLwYVDorNeBA@mail.gmail.com>

On Wed, 20 Jul 2016, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> In 4.8 we have a shiny new kernel doc toolchain:
>
> https://lwn.net/Articles/692705/
>
> I think it'd be great if interested parties (might be just a hallway
> track) sit together and figure out how to best go about converting all
> the existing docs over, and how to link it all together. I think we
> pretty much have agreement that the docbook horror show needs to die,
> but there's lots of other documentation that I think would be great to
> include in the overall (cross-linked!) kernel docs.
>
> People who would be great to be there:
> - Jon Corbet
> - Mauro Carvalho
> - Jani Nikula
> - Markus Heiser
> - maybe Grant Likely, he made noises about sphinx/rst too
>
> I think converting/polishing docs would also serve well as kernel
> newbie task in opw or gsoc or wherever, that might be another
> interested group. And anyone else who wants to convert over docs for
> their subsystem.
>
> Mostly I'm just sending this out to gauge interest.

Perhaps this is redundant, but for the record, I'm interested.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center

      parent reply	other threads:[~2016-08-02 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 11:56 Daniel Vetter
2016-07-20 12:03 ` Julia Lawall
2016-07-20 12:40 ` Mauro Carvalho Chehab
2016-07-20 23:10 ` Jonathan Corbet
2016-07-29 11:00   ` Laurent Pinchart
2016-08-01 10:40   ` Johannes Berg
2016-08-02 14:34 ` Jani Nikula [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=87y44fqlww.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=grant.likely@linaro.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@osg.samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox