From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH RESEND next 1/2] net: can: mscan: add a comment on reg to idx mapping
Date: Sun, 25 Aug 2013 18:42:01 +0200 [thread overview]
Message-ID: <521A33D9.7050605@hartkopp.net> (raw)
In-Reply-To: <52174782.6080002@pengutronix.de>
On 23.08.2013 13:29, Marc Kleine-Budde wrote:
> 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.
For net-next or for net?
When this stuff would be for net-next i could add a new feature for can-gw too ...
So that there's not always only one lonely item to pull for Dave ;-)
Regards,
Oliver
next prev parent reply other threads:[~2013-08-25 16:42 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 ` [PATCH RESEND next 1/2] net: can: mscan: add a comment on reg to idx mapping Marc Kleine-Budde
2013-08-25 16:42 ` Oliver Hartkopp [this message]
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=521A33D9.7050605@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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).