All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: jamal <hadi@cyberus.ca>, "David S. Miller" <davem@davemloft.net>,
	netdev@oss.sgi.com
Subject: Re: [PATCH] PKT_SCHED: Fix cls indev validation
Date: Wed, 22 Dec 2004 10:36:48 +0100	[thread overview]
Message-ID: <41C94030.4050806@trash.net> (raw)
In-Reply-To: <20041222003142.GB7884@postel.suug.ch>

Thomas Graf wrote:
> * Patrick McHardy <41C7F833.4000909@trash.net> 2004-12-21 11:17
> 
>>I'm not sure which areas of the code I can still
>>touch without conflicting with you :)
> 
> 
>  include/linux/pkt_cls.h   |    6 
>  include/linux/rtnetlink.h |    3 
>  include/net/pkt_cls.h     |   45 +++++
>  net/sched/cls_api.c       |  205 +++++++++++++++++++++++++
>  net/sched/cls_fw.c        |  145 +++---------------
>  net/sched/cls_route.c     |  355 ++++++++++++++++++++++++--------------------
>  net/sched/cls_rsvp.h      |   88 +++++------
>  net/sched/cls_tcindex.c   |  364 +++++++++++++++++++++++++---------------------
>  net/sched/cls_u32.c       |  131 ++++------------
>  9 files changed, 766 insertions(+), 576 deletions(-)

Thanks. I'm going to take on the action code then.

Regards
Patrick

  reply	other threads:[~2004-12-22  9:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-19 20:30 [PATCH] PKT_SCHED: Fix cls indev validation Thomas Graf
2004-12-20  8:27 ` Patrick McHardy
2004-12-20 13:03   ` Thomas Graf
2004-12-20 14:16   ` jamal
2004-12-20 20:07     ` Thomas Graf
2004-12-21 10:17       ` Patrick McHardy
2004-12-22  0:31         ` Thomas Graf
2004-12-22  9:36           ` Patrick McHardy [this message]
2004-12-22 13:32           ` jamal
2004-12-22 14:26             ` Thomas Graf
2004-12-28 13:27               ` jamal
2004-12-21  0:22     ` Thomas Graf
2004-12-21  0:56       ` David S. Miller

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=41C94030.4050806@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    --cc=tgraf@suug.ch \
    /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.