From: Roman Kagan <rkagan@mail.ru>
To: chas3@users.sourceforge.net
Cc: netdev@oss.sgi.com, linux-atm-general@lists.sourceforge.net,
usbatm@lists.infradead.org
Subject: Re: [Linux-ATM-General] [RFC][PATCH] Very basic sysfs support for ATM devices (updated)
Date: Sun, 6 Feb 2005 22:19:18 +0300 [thread overview]
Message-ID: <20050206191918.GA2369@katya> (raw)
In-Reply-To: <200502060133.j161XIj3007281@ginger.cmf.nrl.navy.mil>
On Sat, Feb 05, 2005 at 08:33:18PM -0500, chas williams - CONTRACTOR wrote:
> In message <20050204201327.GA2439@katya>,Roman Kagan writes:
> >initializing atm_dev. I suspect the only way to fix it is to split the
> >atm_dev initialization into two stages, allocation and registration, as
> >it is done for net_device.
>
> yeah which is why i just wanted to convert atm_dev to just be a netdevice.
> the code is already written and "stable".
Is it publically available? Linux-ATM CVS appears to contain no
kernelspace code. I'm just curious how atm_dev attributes are mapped to
net_device's, which doesn't look easy with the current atm_dev and
net_device.
Also, is it scheduled for inclusion in the mainline any time soon? If
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?
Roman.
next prev parent reply other threads:[~2005-02-06 19:19 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 [this message]
2005-02-08 15:02 ` chas williams - CONTRACTOR
2005-02-08 16:45 ` Roman Kagan
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=20050206191918.GA2369@katya \
--to=rkagan@mail.ru \
--cc=chas3@users.sourceforge.net \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=usbatm@lists.infradead.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 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.