From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: sparclinux@vger.kernel.org
Subject: Re: Enable module aliases for vio on sparc/sparc64
Date: Wed, 13 Apr 2016 23:04:17 +0000 [thread overview]
Message-ID: <570ED071.60804@physik.fu-berlin.de> (raw)
In-Reply-To: <570B52AE.8080603@physik.fu-berlin.de>
On 04/14/2016 01:01 AM, David Miller wrote:
> Ok those are the block devices, where are the networking interfaces?
Whoops, sorry:
root@deb4g:/sys/devices/channel-devices# cat vdc*/mod*
vio:Tvdc-portSunknown
vio:Tvdc-portSunknown
vio:Tvdc-portSunknown
vio:Tvdc-portSunknown
vio:Tvdc-portSunknown
root@deb4g:/sys/devices/channel-devices#
Testing a much simpler version now. Second.
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2016-04-13 23:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 7:30 Enable module aliases for vio on sparc/sparc64 John Paul Adrian Glaubitz
2016-04-11 19:04 ` David Miller
2016-04-12 9:29 ` John Paul Adrian Glaubitz
2016-04-13 15:33 ` John Paul Adrian Glaubitz
2016-04-13 22:23 ` David Miller
2016-04-13 22:35 ` John Paul Adrian Glaubitz
2016-04-13 22:36 ` David Miller
2016-04-13 22:37 ` David Miller
2016-04-13 22:44 ` John Paul Adrian Glaubitz
2016-04-13 23:01 ` David Miller
2016-04-13 23:04 ` John Paul Adrian Glaubitz [this message]
2016-04-13 23:22 ` John Paul Adrian Glaubitz
2016-04-14 1:52 ` David Miller
2016-04-14 1:52 ` David Miller
2016-04-14 1:53 ` David Miller
2016-04-14 9:00 ` John Paul Adrian Glaubitz
2016-04-14 9:10 ` John Paul Adrian Glaubitz
2016-04-14 10:27 ` Sam Ravnborg
2016-04-14 10:52 ` John Paul Adrian Glaubitz
2016-04-14 13:30 ` Sam Ravnborg
2016-04-14 16:00 ` John Paul Adrian Glaubitz
2016-04-14 16:02 ` David 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=570ED071.60804@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=sparclinux@vger.kernel.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.