From: "David S. Miller" <davem@davemloft.net>
To: Patrick McHardy <kaber@trash.net>
Cc: vanco@satro.sk, netdev@oss.sgi.com
Subject: Re: 2.6.11 on AMD64 traps
Date: Wed, 9 Mar 2005 16:43:04 -0800 [thread overview]
Message-ID: <20050309164304.5902e558.davem@davemloft.net> (raw)
In-Reply-To: <422F8D84.8010103@trash.net>
On Thu, 10 Mar 2005 00:57:56 +0100
Patrick McHardy <kaber@trash.net> wrote:
> > Will this patch be included in future kernels?
>
> I hope so. Dave, are you fine with making /proc more efficient than
> netlink ? :)
No objection :-) I'll hit this on my next pass over my 2.6.x
backlog which should start tonight.
next prev parent reply other threads:[~2005-03-10 0:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503081900.18686.vanco@satro.sk>
2005-03-08 18:35 ` 2.6.11 on AMD64 traps Andre Tomt
2005-03-09 19:45 ` Patrick McHardy
2005-03-09 20:24 ` Michal Vanco
2005-03-09 20:34 ` Patrick McHardy
2005-03-09 20:42 ` Michal Vanco
2005-03-09 21:05 ` Patrick McHardy
2005-03-09 21:17 ` Michal Vanco
2005-03-09 23:27 ` Patrick McHardy
2005-03-09 23:50 ` Michal Vanco
2005-03-09 23:57 ` Patrick McHardy
2005-03-10 0:43 ` David S. Miller [this message]
2005-03-11 2:20 ` 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=20050309164304.5902e558.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.com \
--cc=vanco@satro.sk \
/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).