From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 51851] New: Unable to use alx driver without CONFIG_MDIO
Date: Thu, 20 Dec 2012 09:25:00 +0000 (UTC) [thread overview]
Message-ID: <bug-51851-58281@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=51851
Summary: Unable to use alx driver without CONFIG_MDIO
Product: Backports project
Version: unspecified
Kernel Version: 3.7.1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Compat-Drivers
AssignedTo: backports@vger.kernel.org
ReportedBy: pfactum@gmail.com
Regression: No
I use own customized kernel in which I've disabled all unnecessary ethernet
drivers. The fact is that new alx driver from 2012-12-19 tree depends on
CONFIG_MDIO, and if I do not select in-kernel driver that depends on it (e.g.,
some broadcom or so), inserting compiled alx module gives me this:
===
[ 44.248978] alx: Unknown symbol mdio_mii_ioctl (err 0)
===
I've got this fixed by adding into drivers/net/ethernet/atheros/Kconfig of my
kernel tree "select MDIO" for Atheros drivers without selecting any other
drivers.
Probably, it's possible to get it fixed in compat-drivers tree?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-12-20 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 9:25 bugzilla-daemon [this message]
2013-04-09 11:24 ` [Bug 51851] Unable to use alx driver without CONFIG_MDIO bugzilla-daemon
2013-06-04 10:59 ` bugzilla-daemon
2013-07-11 22:53 ` bugzilla-daemon
2013-07-30 14:09 ` bugzilla-daemon
2013-11-19 16:55 ` [Bug 51851] [TRIVIAL]Unable " bugzilla-daemon
2013-11-24 19:29 ` bugzilla-daemon
2013-11-24 19:29 ` bugzilla-daemon
2013-11-24 19:30 ` bugzilla-daemon
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=bug-51851-58281@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=backports@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.