From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Mugunthan V N <mugunthanvnm@ti.com>,
Wolfgang Grandegger <wg@grandegger.com>
Cc: Pavel Machek <pavel@denx.de>, Thor Thayer <tthayer@altera.com>,
Prabhakar Lad <prabhakar.csengg@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Wolfram Sang <wsa@sang-engineering.com>,
Chen Gang <gang.chen@asianux.com>,
George Cherian <george.cherian@ti.com>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [can-next PATCH 1/1] net: can: c_can_platform: Use devm_ioremap instead of devm_ioremap_resource.
Date: Fri, 25 Jul 2014 09:38:27 +0200 [thread overview]
Message-ID: <53D20973.108@pengutronix.de> (raw)
In-Reply-To: <1406269181-4092-1-git-send-email-mugunthanvnm@ti.com>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On 07/25/2014 08:19 AM, Mugunthan V N wrote:
> From: George Cherian <george.cherian@ti.com>
>
> The raminit register is shared register for both can0 and can1.
> Using devm_ioremap_resource fails the mapping for can1 interface
> leading to a non functional can interface.
>
> Signed-off-by: George Cherian <george.cherian@ti.com>
> Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
Applied to can, I've adjusted the commit message a bit, mentioning the
patch, that introduced the regression.
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: 242 bytes --]
next prev parent reply other threads:[~2014-07-25 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 6:19 [can-next PATCH 1/1] net: can: c_can_platform: Use devm_ioremap instead of devm_ioremap_resource Mugunthan V N
2014-07-25 7:38 ` Marc Kleine-Budde [this message]
2014-07-25 10:49 ` Wolfram Sang
2014-07-25 13:06 ` Marc Kleine-Budde
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=53D20973.108@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=gang.chen@asianux.com \
--cc=george.cherian@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pavel@denx.de \
--cc=prabhakar.csengg@gmail.com \
--cc=tglx@linutronix.de \
--cc=tthayer@altera.com \
--cc=wg@grandegger.com \
--cc=wsa@sang-engineering.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).