From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
linux-aspeed@lists.ozlabs.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Andrew Jeffery <andrew@aj.id.au>,
Jonathan Corbet <corbet@lwn.net>,
Liviu Dudau <liviu.dudau@arm.com>,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Paul Mackerras <paulus@samba.org>, Joel Stanley <joel@jms.id.au>,
linuxppc-dev@lists.ozlabs.org,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 00/21] Convert hwmon documentation to ReST
Date: Thu, 11 Apr 2019 20:54:17 -0300 [thread overview]
Message-ID: <20190411205417.187f9565@coco.lan> (raw)
In-Reply-To: <20190411210731.GA29378@roeck-us.net>
Em Thu, 11 Apr 2019 14:07:31 -0700
Guenter Roeck <linux@roeck-us.net> escreveu:
> On Thu, Apr 11, 2019 at 05:43:57PM -0300, Mauro Carvalho Chehab wrote:
> > Em Thu, 11 Apr 2019 12:43:24 -0600
> > Jonathan Corbet <corbet@lwn.net> escreveu:
> >
> > > On Wed, 10 Apr 2019 16:22:37 -0300
> > > Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> > >
> > > > This series converts the contents of Documentation/hwmon to ReST
> > > > format.
> > > >
> > > > PS.: I opted to group the conversion files per groups of maintainer
> > > > set, as, if I were to generate one patch per file, it would give around
> > > > 160 patches.
> > > >
> > > > I also added those patches to my development tree at:
> > > > https://git.linuxtv.org/mchehab/experimental.git/log/?h=hwmon
> > > >
> > > > If you want to see the results, they're at:
> > > > https://www.infradead.org/~mchehab/hwmon/
> > >
> > > This set seems generally good and could probably be applied as-is. But I
> > > have to ask...is there a reason to not take the last step and actually
> > > bring this stuff into the Sphinx doc tree?
> > >
> > > We seem to be mostly documenting sysfs files and such. I am *guessing*
> > > that perhaps the set should move to Documentation/admin-guide/hwmon? Or
> > > have I misunderstood the intended audience here?
> >
> > :-)
> >
> > Yeah, I'd say that 80% of the contents there are user-faced.
> >
> > Yet, the main issue with this (and other driver subsystems) is that there's
> > a mix of userspace and Kernelspace stuff. One somewhat simple case is
> > the abituguru: it has a "datasheet" file:
> >
> > abituguru-datasheet
> >
> > This contains programming information for the corresponding drivers,
> > while abituguru and abituguru3 contains mostly userspace
> > stuff (still, it also contains the I2C address, with shouldn't mean
> > anything for the user).
> >
> > However, if you take a look at w83781d, you'll see a mix of both
> > userspace and driver developer info there... it has a chapter called
> > "Data sheet updates", for example, with is probably meaningless for
> > anyone but the hwmon driver developers.
> >
> > That's, btw, a pattern that happens a lot inside device driver
> > documents on almost all subsystems I checked: driver-specific
> > documentation is usually not split into user-facing/kernel-facing.
> >
> > While nobody does such split, IMHO, the best would be to keep the
> > information outside Documentation/admin-guide. But hey! You're
> > the Doc maintainer. If you prefer to move, I'm perfectly fine
> > with that.
> >
>
> Same here, but please don't move the files which are kernel facing only.
>
> How do you want to handle this series ? Do you expect it to be pushed
> through hwmon, or through Documentation, or do you plan to push yourself ?
>
> If the series isn't pushed through hwmon, we'll likely have a couple of
> conflicts against hwmon-next.
Guenter,
I won't be pushing it myself. IMO, it makes more sense to apply it at
hwmon-next, except if it would cause some conflicts against docs-next.
Regards,
Mauro
next prev parent reply other threads:[~2019-04-11 23:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 19:22 [PATCH v2 00/21] Convert hwmon documentation to ReST Mauro Carvalho Chehab
2019-04-10 19:22 ` [PATCH v2 11/21] docs: hwmon: ibmpowernv: convert to ReST format Mauro Carvalho Chehab
2019-04-10 19:22 ` [PATCH v2 21/21] docs: hwmon: Add an index file and rename docs to *.rst Mauro Carvalho Chehab
2019-04-11 13:07 ` Liviu Dudau
2019-04-11 18:43 ` [PATCH v2 00/21] Convert hwmon documentation to ReST Jonathan Corbet
2019-04-11 20:43 ` Mauro Carvalho Chehab
2019-04-11 21:07 ` Guenter Roeck
2019-04-11 23:54 ` Mauro Carvalho Chehab [this message]
2019-04-12 16:04 ` Jonathan Corbet
2019-04-12 16:12 ` Guenter Roeck
2019-04-13 0:25 ` Mauro Carvalho Chehab
2019-04-13 0:52 ` Guenter Roeck
2019-04-13 3:09 ` Guenter Roeck
2019-04-16 20:19 ` Jonathan Corbet
2019-04-16 20:31 ` Guenter Roeck
2019-04-17 1:58 ` Mauro Carvalho Chehab
2019-04-17 3:49 ` Guenter Roeck
2019-04-17 9:47 ` Mauro Carvalho Chehab
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=20190411205417.187f9565@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=andrew@aj.id.au \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=mchehab@infradead.org \
--cc=paulus@samba.org \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).