All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Kagan <rkagan@mail.ru>
To: netdev@oss.sgi.com, linux-atm-general@lists.sourceforge.net
Subject: Re: [Linux-ATM-General] [RFC][PATCH] Very basic sysfs support for ATM devices (updated)
Date: Tue, 8 Feb 2005 19:45:47 +0300	[thread overview]
Message-ID: <20050208164547.GA2928@katya> (raw)
In-Reply-To: <200502081502.j18F2ITI010672@ginger.cmf.nrl.navy.mil>

On Tue, Feb 08, 2005 at 10:02:19AM -0500, chas williams - CONTRACTOR wrote:
> >it is, maybe we shouldn't create an atm-specific user-visible interface
> >in sysfs and hotplug which is going to be obsoleted by the net generic
> >one in the near future?
> 
> with sysfs support the only thing left to 'fix' would be splitting of
> allocation/registration.

I beg your pardon, but are you saying that you've changed your mind re.
moving to net_device?  Is your plan now to cast in stone that ATM
devices live under class/atm in sysfs, and go ahead with splitting of
allocation/registration of the current atm_dev?

Roman.

  reply	other threads:[~2005-02-08 16:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050119174543.GA2418@katya>
2005-01-21  8:51 ` [RFC][PATCH] Very basic sysfs support for ATM devices (updated) Roman Kagan
2005-02-04 18:11   ` [Linux-ATM-General] " chas williams - CONTRACTOR
2005-02-04 18:27     ` matthieu castet
2005-02-04 18:50       ` chas williams - CONTRACTOR
2005-02-04 20:13     ` Roman Kagan
2005-02-06  1:33       ` chas williams - CONTRACTOR
2005-02-06 19:19         ` Roman Kagan
2005-02-08 15:02           ` chas williams - CONTRACTOR
2005-02-08 16:45             ` Roman Kagan [this message]
2005-02-07  9:03       ` Duncan Sands
2005-02-07  9:45         ` Roman Kagan

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=20050208164547.GA2928@katya \
    --to=rkagan@mail.ru \
    --cc=linux-atm-general@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.