netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: Meelis Roos <mroos@linux.ee>, netdev <netdev@oss.sgi.com>
Subject: Re: cls_u32 compile failure in current 2.6.12-rc1+BK tree
Date: Mon, 28 Mar 2005 14:38:01 +0200	[thread overview]
Message-ID: <20050328123801.GY3086@postel.suug.ch> (raw)
In-Reply-To: <1112012657.1089.1013.camel@jzny.localdomain>

* jamal <1112012657.1089.1013.camel@jzny.localdomain> 2005-03-28 07:24
> If we are going to make u32 an exception then this code should be
> surrounded by #ifdef ..ACTION..

The same condition is needed for tcf_exts_dump and tcf_exts_dump_stats
in u32, they're only apart to cut the TCA_OPTIONS nested TLV so I'm
trying to find out is whether we can get rid of dump_stats alltogether
and hide it. I'm working on a patch to do this, I hope to have enough time
to finish it today.

> My time is about to become scarce, so if you
> have time please create the patch.

Again, don't waste cycles on this. It was my fault and I will fix it. ;->

  reply	other threads:[~2005-03-28 12:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27 19:49 cls_u32 compile failure in current 2.6.12-rc1+BK tree Meelis Roos
2005-03-28  1:07 ` jamal
2005-03-28  7:18   ` Meelis Roos
2005-03-28 12:24     ` jamal
2005-03-28 12:38       ` Thomas Graf [this message]
2005-03-28 12:51         ` jamal
2005-03-28 12:58           ` Thomas Graf
2005-03-28 13:15             ` jamal
2005-03-28 15:55               ` Thomas Graf
2005-03-28 19:28                 ` jamal
2005-03-28 19:53                   ` Thomas Graf
2005-03-28 22:33                     ` Thomas Graf
2005-03-29  1:10                       ` Thomas Graf
2005-03-29 20:51                         ` jamal
2005-03-30  1:02                           ` Thomas Graf
2005-03-30 11:55                             ` jamal
2005-03-31  0:58                             ` 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=20050328123801.GY3086@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=hadi@cyberus.ca \
    --cc=mroos@linux.ee \
    --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 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).