From: Max Krasnyansky <maxk@qualcomm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: acme@conectiva.com.br, linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [BK ChangeSet@1.1118.1.1] new module infrastructure for net_proto_family
Date: Thu, 24 Apr 2003 09:43:42 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20030424093305.08115dc8@unixmail.qualcomm.com> (raw)
In-Reply-To: <20030423.202954.85407627.davem@redhat.com>
At 08:29 PM 4/23/2003, David S. Miller wrote:
> From: Max Krasnyansky <maxk@qualcomm.com>
> Date: Wed, 23 Apr 2003 18:41:56 -0700
>
> At 04:30 PM 4/23/2003, David S. Miller wrote:
> >Your stuff was unacceptable from the start because you didn't put
> >the ->owner into the protocol ops.
> But you didn't tell me that. You just said that it's "an ugly hack" without
> giving any other feedback.
>
>As you mention, Rusty said this.
>
> What about this though
>
>I'm sure Arnaldo will deal with the sys_accept() issues.
>But this is a minor issue, Arnaldo's stuff is architectually
>solid.
:)
Ok Dave. I'm not sure why you're _completely_ ignoring my arguments.
You should have just said from the beginning that you were going to
ignore what I have to say regarding that issue. At least I wouldn't
have wasted my time.
Sorry for bugging you.
Max
next prev parent reply other threads:[~2003-04-24 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 19:13 [BK ChangeSet@1.1118.1.1] new module infrastructure for net_proto_family Max Krasnyansky
2003-04-23 19:26 ` Arnaldo Carvalho de Melo
2003-04-23 22:51 ` Max Krasnyansky
2003-04-23 23:30 ` David S. Miller
2003-04-24 1:41 ` Max Krasnyansky
2003-04-24 3:29 ` David S. Miller
2003-04-24 16:43 ` Max Krasnyansky [this message]
2003-04-24 6:44 ` Arnaldo Carvalho de Melo
2003-04-24 19:33 ` Max Krasnyansky
2003-04-24 23:02 ` Arnaldo Carvalho de Melo
2003-04-25 0:40 ` Max Krasnyansky
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=5.1.0.14.2.20030424093305.08115dc8@unixmail.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=acme@conectiva.com.br \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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).