From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Anatolij Gustschin <agust@denx.de>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Gerhard Sittig <gsi@denx.de>,
linux-can@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH RESEND next 1/2] net: can: mscan: add a comment on reg to idx mapping
Date: Fri, 23 Aug 2013 13:29:06 +0200 [thread overview]
Message-ID: <52174782.6080002@pengutronix.de> (raw)
In-Reply-To: <1377256144-4173-1-git-send-email-agust@denx.de>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On 08/23/2013 01:09 PM, Anatolij Gustschin wrote:
> From: Gerhard Sittig <gsi@denx.de>
>
> add a comment about the magic of deriving an MSCAN component index
> from the peripheral's physical address / register offset
>
> Cc: linux-can@vger.kernel.org
> Cc: netdev@vger.kernel.org
> Signed-off-by: Gerhard Sittig <gsi@denx.de>
> Signed-off-by: Anatolij Gustschin <agust@denx.de>
Tnx, both applied to linux-can-next/testing. Will be included in the net
pull request to Daivd.
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:[~2013-08-23 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 11:09 [PATCH RESEND next 1/2] net: can: mscan: add a comment on reg to idx mapping Anatolij Gustschin
2013-08-23 11:09 ` [PATCH RESEND next 2/2] net: can: mscan: improve clock API use Anatolij Gustschin
2013-08-23 11:29 ` Marc Kleine-Budde [this message]
2013-08-25 16:42 ` [PATCH RESEND next 1/2] net: can: mscan: add a comment on reg to idx mapping Oliver Hartkopp
2013-08-26 7:20 ` Marc Kleine-Budde
2013-08-29 15:29 ` Oliver Hartkopp
2013-08-29 21:14 ` 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=52174782.6080002@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=agust@denx.de \
--cc=gsi@denx.de \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.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.