From: Benoit Cousson <b-cousson@ti.com>
To: AnilKumar Ch <anilkumar@ti.com>
Cc: wg@grandegger.com, mkl@pengutronix.de, swarren@wwwdotorg.org,
linux-can@vger.kernel.org, tony@atomide.com,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
grant.likely@secretlab.ca, devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH 0/3] can: Add D_CAN raminit support to am335x-evm
Date: Wed, 9 Jan 2013 13:16:37 +0100 [thread overview]
Message-ID: <50ED5FA5.9020305@ti.com> (raw)
In-Reply-To: <1352916505-12343-1-git-send-email-anilkumar@ti.com>
Hi Anil,
On 11/14/2012 07:08 PM, AnilKumar Ch wrote:
> This patch series adds d_can raminit support to c_can/d_can driver,
> which is required to init/de-init D_CAN message RAM (holds message
> objects). Added corresponding DT changes to get resource of RAMINIT
> register and device instance.
>
> These patches were tested on AM335x-EVM along with pinctrl data addition
> patch, which is not added to am335x-evm.dts (only supports CPLD profile#0)
> because d_can1 is supported under CPLD profile#1.
>
> AnilKumar Ch (3):
> can: c_can: Add d_can raminit support
> ARM: dts: AM33XX: Add d_can instances to aliases
> ARM: dts: AM33XX: Add memory resource to d_can node
I've just applied both DTS patches with Acked-by from Marc in my
for_3.9/dts branch.
Regards,
Benoit
next prev parent reply other threads:[~2013-01-09 12:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 18:08 [PATCH 0/3] can: Add D_CAN raminit support to am335x-evm AnilKumar Ch
2012-11-14 18:08 ` [PATCH 1/3] can: c_can: Add d_can raminit support AnilKumar Ch
[not found] ` <1352916505-12343-2-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-11-20 10:50 ` Marc Kleine-Budde
2012-11-20 13:05 ` AnilKumar, Chimata
2012-11-20 13:46 ` Marc Kleine-Budde
[not found] ` <1352916505-12343-1-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-11-14 18:08 ` [PATCH 2/3] ARM: dts: AM33XX: Add d_can instances to aliases AnilKumar Ch
[not found] ` <1352916505-12343-3-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-11-20 10:51 ` Marc Kleine-Budde
2013-01-02 10:13 ` AnilKumar, Chimata
2012-11-20 5:00 ` [PATCH 0/3] can: Add D_CAN raminit support to am335x-evm AnilKumar, Chimata
2012-11-14 18:08 ` [PATCH 3/3] ARM: dts: AM33XX: Add memory resource to d_can node AnilKumar Ch
2012-11-20 10:13 ` Marc Kleine-Budde
2012-11-20 10:23 ` AnilKumar, Chimata
[not found] ` <331ABD5ECB02734CA317220B2BBEABC13EA7701D-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-11-20 10:26 ` Marc Kleine-Budde
2012-11-21 5:45 ` AnilKumar, Chimata
[not found] ` <331ABD5ECB02734CA317220B2BBEABC13EA778F3-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-11-21 8:20 ` Marc Kleine-Budde
2012-11-21 8:20 ` Marc Kleine-Budde
2013-01-02 10:14 ` AnilKumar, Chimata
2013-01-09 12:16 ` Benoit Cousson [this message]
2013-01-09 12:20 ` [PATCH 0/3] can: Add D_CAN raminit support to am335x-evm 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=50ED5FA5.9020305@ti.com \
--to=b-cousson@ti.com \
--cc=anilkumar@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=swarren@wwwdotorg.org \
--cc=tony@atomide.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).