linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <acourbot@nvidia.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Documentation: gpiolib: document new interface
Date: Wed, 04 Dec 2013 19:35:19 -0600	[thread overview]
Message-ID: <1386207319.1974.312@driftwood> (raw)
In-Reply-To: <CAAVeFuLqRBrHShK-gvmRHyDJ5c3gdKJJwX1UKNNTLCCUbVczKg@mail.gmail.com> (from gnurou@gmail.com on Sun Nov 24 00:02:30 2013)

On 11/24/2013 12:02:30 AM, Alexandre Courbot wrote:
> Hi Rob,
> 
> On Sun, Nov 24, 2013 at 8:31 AM, Rob Landley <rob@landley.net> wrote:
> >> > Linus, I hope this can be merged during the -rc cycle of 3.13,  
> since the
> >> > gpiod_ interface is going to be introduced there. It would not  
> make much
> >> > sense for it to come without its documentation.
> >>
> >> You're right of course. I'll read through it and apply fixes on top
> >> (or squash into your patch.)
> >>
> >> Formal stuff:
> >> Don't we need an 00-INDEX file?
> >> (Maybe Rob can tell whether this is desirable.)
> >
> >
> > A 00-INDEX file wouldn't hurt, but it can always be added later. No  
> reason
> > to hold up the series for that. (I was using them to generate html  
> indexes
> > for kernel.org/doc but after the breakin they eliminated all non-git
> > functionality so I haven't been able to update it since. They  
> replaced
> > kernel.org/doc/Documentation with a raw git checkout, and I expect  
> them to
> > replace kernel.org/doc/menuconfig with a raw git checkout any day  
> now.)
> >
> > That said, a 00-INDEX file would let you know where to start  
> reading to find
> > the file with the intro paragraph at the start of the old file, the  
> bit
> > explaining what GPIO is. Here the first file alphabetically is  
> "board.txt",
> > and I have no idea why it's named that, given how it starts. (I was  
> sort of
> > hoping that somebody who already knows the subsystem would comment  
> before I
> > do. I have no way of knowing if this documentation is _right_.)
> 
> I actually submitted a patch that introduces a 00-INDEX file
> yesterday. It's probably a few other gazillions mails under in your
> inbox. ;)

I'm a couple weeks behind on my email. I'll get to it eventually. (My  
time's spread between a few too many projects these days...)

Most documentation goes in through the trees of the people whose  
subsystems it documents. I mostly catch the stuff that falls through  
the cracks. I'm somewhere between a librarian shelving abandoned books  
and a janitor.

...
> > But I really don't have time to go through every paragraph like  
> that, and
> > was hoping the gpio guys would (or just sign off on it so I don't  
> have
> > to)...
> 
> I will make another pass and send an update (or a new version of the
> patch maybe, since we are still in -rc1 - whatever is more convenient
> to Linus). Hopefully early users of the new (oops) interface will send
> fixes to the documentation as well, if only to improve my approximate
> English.

It's not so much the english, it's that Documentation should be aimed  
at people who _don't_ already know this stuff. Since it tends to be  
written by people who _do_ already know the stuff (kinda hard to do the  
other way, although I've done it), this can be tricky to pull off. You  
have to maintain a "But what if this _wasn't_ a rhetorical question?"  
mindset and emulate a Virtual Newbie. (I suggest qemu for this.)

Still, thanks for taking a stab at it. Imperfect's better than  
obsolete...

Rob

      reply	other threads:[~2013-12-05  2:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-16 12:34 [PATCH v2] Documentation: gpiolib: document new interface Alexandre Courbot
2013-11-18  9:34 ` Linus Walleij
2013-11-18 10:33   ` Alex Courbot
2013-11-19  9:32     ` Linus Walleij
2013-11-23 23:31   ` Rob Landley
2013-11-24  6:02     ` Alexandre Courbot
2013-12-05  1:35       ` Rob Landley [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=1386207319.1974.312@driftwood \
    --to=rob@landley.net \
    --cc=acourbot@nvidia.com \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).