From: Grant Likely <grant.likely@secretlab.ca>
To: Jean Delvare <khali@linux-fr.org>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
Dirk Eibach <eibach@gdsys.de>,
devicetree-discuss@lists.ozlabs.org, rdunlap@xenotime.net,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] hwmon: (ads1015) Add devicetree documentation
Date: Thu, 17 Mar 2011 10:46:49 -0600 [thread overview]
Message-ID: <20110317164649.GE9597@angua.secretlab.ca> (raw)
In-Reply-To: <20110317112530.50dc4915@endymion.delvare>
On Thu, Mar 17, 2011 at 11:25:30AM +0100, Jean Delvare wrote:
> On Thu, 3 Mar 2011 15:09:28 -0700, Grant Likely wrote:
> > On Thu, Mar 3, 2011 at 3:02 PM, Jean Delvare <khali@linux-fr.org> wrote:
> > > I will leave it up to Dirk to decide how much time he wants to spend on
> > > this. He has already been very patient with the driver review process
> > > and I do not want to abuse his patience.
> >
> > BTW Dirk, I'm happy to help show how to write the parser code for the
> > sub-node approach if you need it.
>
> Grant, Wolfram, how are such patches committed? Documentation/devicetree/
> isn't listed in MAINTAINERS. Is it OK for me to commit it once Dirk gets
> your approval? Or do you prefer to commit it yourself?
Yup. It makes sense for the documentation to be committed along side
the driver changes. I have no problem with you taking this patch.
g.
next prev parent reply other threads:[~2011-03-17 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 9:16 [PATCH] hwmon: (ads1015) Add devicetree documentation Dirk Eibach
2011-03-03 11:51 ` Wolfram Sang
2011-03-03 12:20 ` Jean Delvare
2011-03-03 13:25 ` Wolfram Sang
2011-03-03 17:26 ` Grant Likely
2011-03-03 22:02 ` Jean Delvare
2011-03-03 22:09 ` Grant Likely
2011-03-17 10:25 ` Jean Delvare
2011-03-17 16:46 ` Grant Likely [this message]
2011-03-03 17:01 ` Grant Likely
2011-03-03 12:32 ` [PATCH v3] " Dirk Eibach
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=20110317164649.GE9597@angua.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=eibach@gdsys.de \
--cc=khali@linux-fr.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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