From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "wg@grandegger.com" <wg@grandegger.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"Gole, Anant" <anantgole@ti.com>, "Nori, Sekhar" <nsekhar@ti.com>
Subject: Re: [PATCH] can: c_can: Add d_can suspend resume support
Date: Fri, 21 Sep 2012 12:25:59 +0200 [thread overview]
Message-ID: <505C40B7.6010902@pengutronix.de> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA389E1@DBDE01.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On 09/21/2012 12:16 PM, AnilKumar, Chimata wrote:
> Hi Marc,
>
> On Fri, Sep 21, 2012 at 15:41:22, Marc Kleine-Budde wrote:
>> On 09/21/2012 11:59 AM, AnilKumar Ch wrote:
>>> Adds suspend resume support to DCAN driver which enables
>>> DCAN power down mode bit (PDR). Then DCAN will ack the local
>>> power-down mode by setting PDA bit in STATUS register.
>>
>> Applied to can-next. I've updated the master branch in the can-next
>
> Thanks for pushing,
>
>> repo. AnilKumar, I think I should squash patch "of: Modify c_can binding
>> documentation" into "can: c_can: Add device tree support to Bosch
>> C_CAN/D_CAN controller". What do you think?
>>
>
> Yes, good to have in a patch where C_CAN DT support is added.
> No issues.
Squashed and pushed.
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 --]
prev parent reply other threads:[~2012-09-21 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 9:59 [PATCH] can: c_can: Add d_can suspend resume support AnilKumar Ch
2012-09-21 10:11 ` Marc Kleine-Budde
2012-09-21 10:16 ` AnilKumar, Chimata
2012-09-21 10:25 ` 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=505C40B7.6010902@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=anantgole@ti.com \
--cc=anilkumar@ti.com \
--cc=linux-can@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 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.