From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Dong Aisheng <dongas86@gmail.com>
Cc: Dong Aisheng <b29396@freescale.com>,
linux-can@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, socketcan@hartkopp.net,
Varka Bhadram <varkabhadram@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
wg@grandegger.com, Grant Likely <grant.likely@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 1/2] can: m_can: add device tree binding documentation
Date: Thu, 14 Aug 2014 11:56:52 +0200 [thread overview]
Message-ID: <53EC87E4.5030107@pengutronix.de> (raw)
In-Reply-To: <CAA+hA=R94tPcEsbtSODPjV9oxM48rrc4gLAFaoXhL+1H4BmUHQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
On 08/14/2014 11:30 AM, Dong Aisheng wrote:
> Ping...
>
> On Wed, Jul 30, 2014 at 7:52 PM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>> On 07/16/2014 11:30 AM, Dong Aisheng wrote:
>>> add M_CAN device tree binding documentation
Applied both to linux-can-next.
Thanks,
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: 181 bytes --]
prev parent reply other threads:[~2014-08-14 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 9:30 [PATCH v5 1/2] can: m_can: add device tree binding documentation Dong Aisheng
2014-07-16 9:30 ` [PATCH v5 2/2] can: m_can: add Bosch M_CAN controller support Dong Aisheng
2014-07-16 9:58 ` Varka Bhadram
2014-07-16 10:38 ` Dong Aisheng
2014-07-16 10:05 ` [PATCH v5 1/2] can: m_can: add device tree binding documentation Marc Kleine-Budde
2014-07-16 10:40 ` Dong Aisheng
2014-07-25 11:53 ` Dong Aisheng
2014-07-30 11:52 ` Marc Kleine-Budde
2014-08-14 9:30 ` Dong Aisheng
2014-08-14 9:56 ` Marc Kleine-Budde [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=53EC87E4.5030107@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=b29396@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=dongas86@gmail.com \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=socketcan@hartkopp.net \
--cc=varkabhadram@gmail.com \
--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).