All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: jamal <hadi@cyberus.ca>
Cc: Maillist netdev <netdev@oss.sgi.com>
Subject: [PATCH PKT_SCHED 0/17]: tc action cleanup + fixes
Date: Thu, 30 Dec 2004 04:39:11 +0100	[thread overview]
Message-ID: <41D3785F.3040909@trash.net> (raw)

Hi Jamal,

here is what I got so far, I'll continue tommorrow. Only compile
tested yet. Please review and comment.

Patrick McHardy:
   o [PKT_SCHED]: Disable broken override bits in pedit action
   o [PKT_SCHED]: Return proper error codes in tcf_pedit_init
   o [PKT_SCHED]: Remove checks for impossible conditions in pedit action
   o [PKT_SCHED]: Clean up pedit action
   o [PKT_SCHED]: Clean up tcf_ipt_init
   o [PKT_SCHED]: Fix missing unlock in ipt action error path
   o [PKT_SCHED]: Remove checks for impossible conditions in ipt action
   o [PKT_SCHED]: Clean up ipt action
   o [PKT_SCHED]: Return -EOPNOTSUPP if gact probability is requested 
but not compiled in
   o [PKT_SCHED]: Return proper error codes in tcf_gact_init
   o [PKT_SCHED]: Remove checks for impossible conditions in gact action
   o [PKT_SCHED: Clean up gact action
   o [PKT_SCHED]: Clean up act_api.c action init path, propagate errors 
properly
   o [PKT_SCHED]: Check TCA_ACT_KIND payload size _before_ copying it
   o [PKT_SCHED]: Remove checks for impossible conditions in act_api.c
   o [PKT_SCHED]: Consistent comparision style in act_api.c
   o [PKT_SCHED]: act_api.c whitespace cleanup
 

Regards
Patrick

             reply	other threads:[~2004-12-30  3:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30  3:39 Patrick McHardy [this message]
2004-12-30  4:56 ` [PATCH PKT_SCHED 0/17]: tc action cleanup + fixes jamal
2004-12-30 12:34   ` Patrick McHardy
2004-12-30 13:30     ` jamal
2004-12-30 14:16       ` Patrick McHardy
2004-12-30 16:10     ` Patrick McHardy
2004-12-31  4:45       ` jamal
2004-12-31  9:54         ` Patrick McHardy
2004-12-31 11:26           ` Thomas Graf
2004-12-31 15:00             ` jamal
2004-12-30 22:12     ` Arnaldo Carvalho de Melo

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=41D3785F.3040909@trash.net \
    --to=kaber@trash.net \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    /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.