From: Rostislav Lisovy <lisovy@gmail.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
netdev@vger.kernel.org, linux-can@vger.kernel.org,
lartc@vger.kernel.org, pisa@cmp.felk.cvut.cz,
sojkam1@fel.cvut.cz
Subject: Re: [PATCH iproute2 v2 0/3] CAN Filter/Classifier
Date: Fri, 27 Jul 2012 16:09:25 +0200 [thread overview]
Message-ID: <1343398165.12164.3.camel@lolumad> (raw)
In-Reply-To: <50129E17.7030602@hartkopp.net>
On Fri, 2012-07-27 at 15:56 +0200, Oliver Hartkopp wrote:
> On 27.07.2012 12:02, Marc Kleine-Budde wrote:
>
> > I'm reposting Rostislav's iproute2 patches, as Stephen requested,
> > during the v3.6 merge window with the corresponding kernel patches
> > already applied.
>
>
> Btw. i think these patches address the original implementation from Rostislav
> using the CAN classifier. The review lead to a completely new implementation
> using ematch. Therefore this patch series is outdated AFAICS.
>
> @Rostislav: Am i correct here?
Hello Oliver;
You are right -- these are the patches for the old "standalone can
filter/classifier" implementation.
I will send correct patches hopefully on Monday/Tuesday.
Regards;
Rostislav
next prev parent reply other threads:[~2012-07-27 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 10:02 [PATCH iproute2 v2 0/3] CAN Filter/Classifier Marc Kleine-Budde
2012-07-27 10:02 ` [PATCH iproute2 v2 1/3] Add missing can.h Marc Kleine-Budde
2012-07-27 10:02 ` [PATCH iproute2 v2 2/3] CAN Filter/Classifier -- Source code Marc Kleine-Budde
2012-07-27 10:02 ` [PATCH iproute2 v2 3/3] CAN Filter/Classifier -- Documentation Marc Kleine-Budde
2012-07-27 13:56 ` [PATCH iproute2 v2 0/3] CAN Filter/Classifier Oliver Hartkopp
2012-07-27 13:58 ` Marc Kleine-Budde
2012-07-27 14:06 ` Oliver Hartkopp
2012-07-27 14:09 ` Rostislav Lisovy [this message]
2012-07-27 16:35 ` Oliver Hartkopp
2012-07-27 16:42 ` Marc Kleine-Budde
2012-08-20 20:06 ` Stephen Hemminger
2012-08-21 6:27 ` Oliver Hartkopp
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=1343398165.12164.3.camel@lolumad \
--to=lisovy@gmail.com \
--cc=lartc@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pisa@cmp.felk.cvut.cz \
--cc=socketcan@hartkopp.net \
--cc=sojkam1@fel.cvut.cz \
/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.