From: Patrick McHardy <kaber@trash.net>
To: hadi@znyx.com
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: patch: namsiz
Date: Sun, 16 Jan 2005 19:49:51 +0100 [thread overview]
Message-ID: <41EAB74F.6060507@trash.net> (raw)
In-Reply-To: <1105900522.1090.798.camel@jzny.localdomain>
Jamal Hadi Salim wrote:
>heres one ive wanted to do for a while - dissociate action name size
>from ifnamsiz. for now set it to namize, but later may change it.
>
The same can be done for sch_api and cls_api. I'll add it to my tree
when I'm done with the current fixes, unfortunately one of them has
to touch basically all files in net/sched and I want to avoid clashes.
Regards
Patrick
next prev parent reply other threads:[~2005-01-16 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 18:35 patch: namsiz Jamal Hadi Salim
2005-01-16 18:49 ` Patrick McHardy [this message]
2005-01-16 18:56 ` Thomas Graf
2005-01-16 19:17 ` Jamal Hadi Salim
2005-01-16 19:32 ` path: module replay jamal
2005-01-16 19:43 ` Patrick McHardy
2005-01-16 19:50 ` Patrick McHardy
2005-01-19 4:26 ` Patrick McHardy
2005-01-19 13:35 ` jamal
2005-01-19 14:02 ` Patrick McHardy
2005-01-24 13:28 ` jamal
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=41EAB74F.6060507@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=hadi@znyx.com \
--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).