From: Andrew Morton <akpm@linux-foundation.org>
To: Ben Dooks <ben@simtec.co.uk>
Cc: ben@fluff.org, linux-kernel@vger.kernel.org,
dbrownell@users.sourceforge.net
Subject: Re: gpiolib: add names file in gpio chip sysfs.
Date: Tue, 29 Sep 2009 12:34:16 -0700 [thread overview]
Message-ID: <20090929123416.06e5a381.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090929104734.GL2698@trinity.fluff.org>
On Tue, 29 Sep 2009 11:47:35 +0100
Ben Dooks <ben@simtec.co.uk> wrote:
> On Tue, Aug 04, 2009 at 04:43:39PM -0700, Andrew Morton wrote:
> > On Mon, 03 Aug 2009 17:55:36 +0100
> > ben@fluff.org wrote:
> > >
> >
> > Did you mean the commit to have an author of ben@fluff.org? I assumed
> > not and rewrote it to
> >
> > Ben Dooks <ben@simtec.co.uk>
> >
> > If you indeed want a different Author: and Signed-off-by: line then
> > please indicate that explicitly by putting a From: line at the top of
> > the changelog.
>
> sorry, occasionally whilst using quilt mail I get this wrong.
>
> > As your MUA didn't fill in the real-name part of the From: address,
> > it's nice to provide a From: line in the changelog so the patch
> > receiver doesn't have to type it in.
> >
> > > Add a 'names' file to the sysfs entries for each chip to show which
> > > have names.
> >
> > Why?
>
> To export this information to the user. That was the only reason.
>
hm, OK. I guess I just won't be understanding what value this patch
has. Hopefully more gpio-inclined people do.
What's the status of this patch now? I have a note that David had
issues with it - did they get resolved somehow?
prev parent reply other threads:[~2009-09-29 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 16:55 gpiolib: add names file in gpio chip sysfs ben
2009-08-04 21:02 ` David Brownell
2009-08-04 23:43 ` Andrew Morton
2009-09-29 10:47 ` Ben Dooks
2009-09-29 19:34 ` Andrew Morton [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=20090929123416.06e5a381.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ben@fluff.org \
--cc=ben@simtec.co.uk \
--cc=dbrownell@users.sourceforge.net \
--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