netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: alex@neterion.com
Cc: caitlinb@broadcom.com, johnpol@2ka.mipt.ru,
	Leonid.Grossman@neterion.com, shemminger@osdl.org,
	netdev@vger.kernel.org
Subject: Re: VJ Channel API - driver level (PATCH)
Date: Thu, 04 May 2006 16:04:32 -0700 (PDT)	[thread overview]
Message-ID: <20060504.160432.48902082.davem@davemloft.net> (raw)
In-Reply-To: <445A84E7.1060906@neterion.com>

From: Alex Aizman <alex@neterion.com>
Date: Thu, 04 May 2006 15:49:11 -0700

> So, what are the requirements?

I will say it a 10th time, "we simply don't know yet."

Please be patient and let us design the net channel infrastructure
properly, then we can think clearly about how hardware might support
things.

Hardware folks are jumping the gun and it's very annoying and takes
precious time away from thinking about and working on the
implementation.

  reply	other threads:[~2006-05-04 23:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 20:40 VJ Channel API - driver level (PATCH) Caitlin Bestler
2006-05-04 22:49 ` Alex Aizman
2006-05-04 23:04   ` David S. Miller [this message]
2006-05-05  9:36     ` Evgeniy Polyakov
2006-05-06  0:35       ` David S. Miller
2006-05-06  8:42         ` Evgeniy Polyakov
2006-05-06  8:57           ` Evgeniy Polyakov
  -- strict thread matches above, loose matches on Subject: below --
2006-05-03 18:12 Caitlin Bestler
2006-05-03 18:49 ` Stephen Hemminger
2006-05-03 17:52 Caitlin Bestler
2006-05-03 15:56 Caitlin Bestler
2006-05-03 18:07 ` Evgeniy Polyakov
2006-05-03 18:45   ` YOSHIFUJI Hideaki / 吉藤英明
2006-05-03 20:35   ` David S. Miller
2006-05-03 13:56 Leonid Grossman
2006-05-03 20:23 ` David S. Miller
2006-05-02 22:53 Alex Aizman
2006-05-02 23:00 ` Stephen Hemminger
2006-05-03  6:47   ` 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=20060504.160432.48902082.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Leonid.Grossman@neterion.com \
    --cc=alex@neterion.com \
    --cc=caitlinb@broadcom.com \
    --cc=johnpol@2ka.mipt.ru \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.org \
    /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).