From: Jean Delvare <khali@linux-fr.org>
To: "Eibach, Dirk" <Eibach@gdsys.de>
Cc: "Wolfram Sang" <w.sang@pengutronix.de>,
<linux-kernel@vger.kernel.org>, <guenter.roeck@ericsson.com>,
<lm-sensors@lm-sensors.org>, <rdunlap@xenotime.net>,
<linux-doc@vger.kernel.org>
Subject: Re: [PATCH v4] hwmon: Add support for Texas Instruments ADS1015
Date: Thu, 3 Mar 2011 08:56:31 +0100 [thread overview]
Message-ID: <20110303085631.53016c75@endymion.delvare> (raw)
In-Reply-To: <48D3D52125C49B43AE880038E2E5314BB5BE6B@SRV101.gdsys.de>
On Thu, 3 Mar 2011 08:49:13 +0100, Eibach, Dirk wrote:
>
>
> > Still, there is a new property defined which _always_ needs
> >
> > a) CCing devicetree-discuss (get_maintainer helps here)
> > b) Documentation in Documentation/devicetree/bindings
> >
> > because it needs to be a lot more stable than platform_data.
>
> Jean, should I supply a v5 with Documentation or should I supply a
> separate patch?
Separate patch. I'm not even the one who will review and apply it.
> > (I already lost the original mail, so I sadly can't forward it)
>
> I have forwarded it to devicetree-discuss.
This is where the review will happen, and where hopefully someone will
pick up the patch.
--
Jean Delvare
next prev parent reply other threads:[~2011-03-03 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 9:26 [PATCH] " Dirk Eibach
2011-02-14 10:22 ` Jean Delvare
2011-02-14 13:21 ` [PATCH v2] " Dirk Eibach
2011-02-16 4:50 ` Guenter Roeck
2011-02-17 12:17 ` Jean Delvare
2011-02-17 12:42 ` Jean Delvare
2011-02-18 10:15 ` [PATCH v3] " Dirk Eibach
2011-02-24 16:48 ` Jean Delvare
2011-02-25 13:18 ` [PATCH v4] " Dirk Eibach
2011-03-02 17:57 ` Jean Delvare
2011-03-02 18:16 ` Wolfram Sang
2011-03-03 7:49 ` (WARNING!!! PGP with incorrect signature) " Eibach, Dirk
2011-03-03 7:56 ` Jean Delvare [this message]
2011-03-03 7:53 ` Eibach, Dirk
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=20110303085631.53016c75@endymion.delvare \
--to=khali@linux-fr.org \
--cc=Eibach@gdsys.de \
--cc=guenter.roeck@ericsson.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=rdunlap@xenotime.net \
--cc=w.sang@pengutronix.de \
/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
all inboxes | Powered by JetHome®