From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Andre Naujoks <nautsch2@googlemail.com>
Subject: Re: [PATCH] can-bcm: initialize ifindex for timeouts without previous frame reception
Date: Mon, 26 Nov 2012 22:42:24 +0100 [thread overview]
Message-ID: <50B3E240.1090709@pengutronix.de> (raw)
In-Reply-To: <50B3E1A8.7030900@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
On 11/26/2012 10:39 PM, Oliver Hartkopp wrote:
> On 26.11.2012 22:37, Marc Kleine-Budde wrote:
>
>> On 11/26/2012 10:24 PM, Oliver Hartkopp wrote:
>>> Set in the rx_ifindex to pass the correct interface index in the case of a
>>> message timeout detection. Usually the rx_ifindex value is set at receive
>>> time. But when no CAN frame has been received the RX_TIMEOUT notification
>>> did not contain a valid value.
>>>
>>> Reported-by: Andre Naujoks <nautsch2@googlemail.com>
>>> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
>>
>> Tnx, I'll send a pull request to David, let's hope the best :)
>
>
> It probably helps to tag this patch as a candidate for stable also.
Tnx, already did :)
https://gitorious.org/linux-can/linux-can/commits/fixes-for-3.7
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: 261 bytes --]
prev parent reply other threads:[~2012-11-26 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 21:24 [PATCH] can-bcm: initialize ifindex for timeouts without previous frame reception Oliver Hartkopp
2012-11-26 21:37 ` Marc Kleine-Budde
2012-11-26 21:39 ` Oliver Hartkopp
2012-11-26 21:42 ` 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=50B3E240.1090709@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=nautsch2@googlemail.com \
--cc=socketcan@hartkopp.net \
/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.