From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
"wg@grandegger.com" <wg@grandegger.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Gole, Anant" <anantgole@ti.com>, "Nori, Sekhar" <nsekhar@ti.com>
Subject: Re: [PATCH v2] of: Modify c_can binding documentation
Date: Thu, 06 Sep 2012 11:30:34 +0200 [thread overview]
Message-ID: <50486D3A.6030000@pengutronix.de> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA27FF8@DBDE01.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
On 09/06/2012 11:26 AM, AnilKumar, Chimata wrote:
> Marc,
>
> On Tue, Sep 04, 2012 at 21:05:17, Stephen Warren wrote:
>> On 09/02/2012 10:54 PM, AnilKumar Ch wrote:
>>> Modify c_can binding documentation according to recent review comments
>>> on device tree data addition patches.
>>>
>>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>>
>> Reviewed-by: Stephen Warren <swarren@nvidia.com>
>>
>>
>
> Can you queue this patch as well for 3.7?
Done. Still something missing?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2012-09-06 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 4:54 [PATCH v2] of: Modify c_can binding documentation AnilKumar Ch
2012-09-04 15:35 ` Stephen Warren
2012-09-06 9:26 ` AnilKumar, Chimata
2012-09-06 9:30 ` Marc Kleine-Budde [this message]
2012-09-06 9:36 ` AnilKumar, Chimata
2012-09-06 9:42 ` Marc Kleine-Budde
2012-09-06 9:44 ` Marc Kleine-Budde
2012-09-06 9:48 ` AnilKumar, Chimata
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=50486D3A.6030000@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=anantgole@ti.com \
--cc=anilkumar@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=swarren@wwwdotorg.org \
--cc=wg@grandegger.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 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).