From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [PATCH can-next v3] can-gw: add a variable limit for CAN frame routings
Date: Fri, 11 Jan 2013 07:56:42 +0100 [thread overview]
Message-ID: <50EFB7AA.8080200@hartkopp.net> (raw)
In-Reply-To: <50EFA90F.5020302@hartkopp.net>
It fits in the original patch and context very well (only 4 lines more).
I'll send a v4 instead after testing.
Sorry for the noise.
Oliver
On 11.01.2013 06:54, Oliver Hartkopp wrote:
> Hello Marc,
>
> once you applied this patch to your can-next tree, please tell me the git URL
> before asking Dave to pull it.
>
> I turned out that this extension for can-gw hops enables an additional
> configuration possibility, i would like to add for the pull request too.
>
> Tnx,
> Oliver
>
>
> On 09.01.2013 21:09, Oliver Hartkopp wrote:
>
>> To prevent a possible misconfiguration (e.g. circular CAN frame routings)
>> limit the number of routings of a single CAN frame to a small variable value.
>>
>> The limit can be specified by the module parameter 'max_hops' (1..6).
>> The default value is 1 (one hop), according to the original can-gw behaviour.
>>
>> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
>>
>> ---
>>
>
>
> (..)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-01-11 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 20:09 [PATCH can-next v3] can-gw: add a variable limit for CAN frame routings Oliver Hartkopp
2013-01-11 5:54 ` Oliver Hartkopp
2013-01-11 6:56 ` Oliver Hartkopp [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=50EFB7AA.8080200@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).