From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 65881] errors compiling after make defconfig-alx
Date: Fri, 13 Dec 2013 16:26:44 +0000 [thread overview]
Message-ID: <bug-65881-58281-yB1lYm0jaT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65881-58281@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=65881
--- Comment #6 from Kenn <kolson@wsd1.org> ---
(In reply to Hauke Mehrtens from comment #5)
> There are some fixes for problems with SLES 11 SP3 in the latest release,
> please try backports-20131206 and report your results.
Thanks! That compiled without any errors!
Unfortunately, the driver did not work for the laptop we were trying to get on
the network. It's an Alienware 17 with Qualcomm LAN Killer E2201 wireless.
Vendor ID 1969 Device ID E091. Unfortunately, I no longer have the device in my
office, so testing any further updates requires extra steps from my colleagues.
However, I will monitor backports releases and try new ones periodically.
Hopefully the NIC in the Alienware notebook will be supported soon.
Thanks again for your help!
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-12-13 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 15:57 [Bug 65881] New: errors compiling after make defconfig-alx bugzilla-daemon
2013-11-26 18:06 ` [Bug 65881] " bugzilla-daemon
2013-11-26 19:12 ` bugzilla-daemon
2013-11-30 0:58 ` bugzilla-daemon
2013-12-02 14:47 ` bugzilla-daemon
2013-12-13 0:20 ` bugzilla-daemon
2013-12-13 16:26 ` bugzilla-daemon [this message]
2013-12-16 8:39 ` bugzilla-daemon
2013-12-16 21:48 ` bugzilla-daemon
2014-07-28 3:31 ` bugzilla-daemon
2016-05-04 21:03 ` 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-65881-58281-yB1lYm0jaT@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.