From: Thierry Reding <thierry.reding@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Milo Kim <milo.kim@ti.com>, Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-pwm@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v3 0/4] LP3943 MFD driver for a GPIO expander and a PWM generator
Date: Sun, 15 Sep 2013 13:17:32 +0200 [thread overview]
Message-ID: <20130915111730.GA9765@ulmo> (raw)
In-Reply-To: <20130912152809.GO11227@lee--X1>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
On Thu, Sep 12, 2013 at 04:28:09PM +0100, Lee Jones wrote:
> > * Documentation
> > From Thierry's suggestion, detailed driver description was moved to
> > 'Documentation/lp3943.txt'.
>
> Really? Why here? Do we really want 1000's of driver docs in /Documentation?
>
> No other driver does this (intel gained from a glancing look).
Well, perhaps the top-level Documentation directory isn't optimal, but I
think it's a lot better than the commit description. Perhaps an 'mfd'
subdirectory could be created where documentation such as this could be
put.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Milo Kim <milo.kim-l0cyMroinI0@public.gmane.org>,
Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-pwm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH v3 0/4] LP3943 MFD driver for a GPIO expander and a PWM generator
Date: Sun, 15 Sep 2013 13:17:32 +0200 [thread overview]
Message-ID: <20130915111730.GA9765@ulmo> (raw)
In-Reply-To: <20130912152809.GO11227@lee--X1>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
On Thu, Sep 12, 2013 at 04:28:09PM +0100, Lee Jones wrote:
> > * Documentation
> > From Thierry's suggestion, detailed driver description was moved to
> > 'Documentation/lp3943.txt'.
>
> Really? Why here? Do we really want 1000's of driver docs in /Documentation?
>
> No other driver does this (intel gained from a glancing look).
Well, perhaps the top-level Documentation directory isn't optimal, but I
think it's a lot better than the commit description. Perhaps an 'mfd'
subdirectory could be created where documentation such as this could be
put.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-09-15 11:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 1:30 [PATCH v3 0/4] LP3943 MFD driver for a GPIO expander and a PWM generator Milo Kim
2013-09-12 1:30 ` Milo Kim
2013-09-12 15:28 ` Lee Jones
2013-09-15 11:17 ` Thierry Reding [this message]
2013-09-15 11:17 ` Thierry Reding
2013-09-15 22:47 ` Milo Kim
2013-09-15 22:47 ` Milo Kim
2013-09-15 22:47 ` Milo Kim
2013-09-20 20:28 ` Linus Walleij
2013-09-20 20:28 ` Linus Walleij
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=20130915111730.GA9765@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=milo.kim@ti.com \
--cc=sameo@linux.intel.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.