From: Jan-Bernd Themann <ossthema@de.ibm.com>
To: John Rose <johnrose@austin.ibm.com>
Cc: Thomas Klein <osstklei@de.ibm.com>,
stefan.roscher@de.ibm.com, Christoph Raisch <RAISCH@de.ibm.com>,
Marcus Eder <MEDER@de.ibm.com>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] ehea: dynamic add / remove port
Date: Wed, 21 Feb 2007 08:38:24 +0100 [thread overview]
Message-ID: <200702210838.24515.ossthema@de.ibm.com> (raw)
In-Reply-To: <1171994215.22669.8.camel@sinatra.austin.ibm.com>
Hi,
> This looks great! Two questions. I would assume that the of_device
> results in a "devspec" file in the sysfs directory for the port? Also,
yes, that is true. There is a devspec file containing the ofdt path in the
port directory.
> is there a way to correlate a logical port to an ethernet interface
> (eth0, etc)?
This is also included. Each logical port has a symbolic link to ethX, done
with the SET_NETDEV_DEV macro.
Regards,
Jan-Bernd
next prev parent reply other threads:[~2007-02-21 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 17:28 [PATCH] ehea: dynamic add / remove port Jan-Bernd Themann
2007-02-20 17:56 ` John Rose
2007-02-21 7:38 ` Jan-Bernd Themann [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-21 16:06 Jan-Bernd Themann
2007-02-21 17:02 ` John Rose
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=200702210838.24515.ossthema@de.ibm.com \
--to=ossthema@de.ibm.com \
--cc=MEDER@de.ibm.com \
--cc=RAISCH@de.ibm.com \
--cc=johnrose@austin.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=osstklei@de.ibm.com \
--cc=stefan.roscher@de.ibm.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).