From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Markus Heiser <markus.heiser@darmarit.de>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
"Nikula, Jani" <jani.nikula@linux.intel.com>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] kernel documentation
Date: Fri, 29 Jul 2016 14:00:04 +0300 [thread overview]
Message-ID: <44550834.xrXSv8h38b@avalon> (raw)
In-Reply-To: <20160720171026.7d9d2c2b@lwn.net>
On Wednesday 20 Jul 2016 17:10:26 Jonathan Corbet wrote:
> On Wed, 20 Jul 2016 13:56:31 +0200 Daniel Vetter wrote:
> > 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 had thought about proposing a similar topic. I think it could also be
> useful to have a brief session on how the new stuff works.
I'd be more interested in that than in a session that discusses the process of
converting existing documentation. It's up to each subsystem to move away from
DocBook, I don't really see what we would have to discuss there.
That being said, in order to make the documentation consistent, we'll need
some level of bikeshedding to decide on guidelines for maintainers and
developers. I don't want to spend the kernel summit bikeshedding, but maybe a
high-level discussion on what we need could be useful.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-07-29 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 11:56 [Ksummit-discuss] [TECH TOPIC] kernel documentation 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 [this message]
2016-08-01 10:40 ` Johannes Berg
2016-08-02 14:34 ` Jani Nikula
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=44550834.xrXSv8h38b@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=grant.likely@linaro.org \
--cc=jani.nikula@linux.intel.com \
--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 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.