From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Bitterli, Felix" <felixb@qca.qualcomm.com>
Cc: "Rodriguez, Luis" <rodrigue@qca.qualcomm.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: compat-drivers ./driver-select ath9k builds i915 as well, breaks my video
Date: Tue, 12 Feb 2013 22:28:29 +0100 [thread overview]
Message-ID: <511AB3FD.4020804@hauke-m.de> (raw)
In-Reply-To: <40F35DA312B2CC468349B21A177FEE633C8AD8A5@NASANEXD02E.na.qualcomm.com>
On 02/12/2013 09:19 PM, Bitterli, Felix wrote:
>>> compat-drivers ./driver-select ath9k builds i915 as well, shouldn't, are
>>> you available for fixing this or do we wait for Luis to get back from
>>> Antarctica?
>> I can not reproduce this with the current version based on linux-next
>>from [0].
>>
>> Hauke
>>
>> [0]: https://www.kernel.org/pub/linux/kernel/projects/backports/2013/02/08/
> Thanks Hauke,
>
> The i915 issue was with stable compat-drivers-3.7.1-3 sorry for omitting that. It is solved with both backports/stable/v3.8-rc7/ and backports/2013/02/08/
>
> Different issue: 'make uninstall' does nothing for me. history|tail -7
> 2020 tar xjvf compat-drivers-2013-02-10.tar.bz2
> 2021 cd compat-drivers-3.8-rc7-1/
> 2022 ./scripts/driver-select ath9k
> 2023 make
> 2024 sudo make install
> 2025 sudo make uninstall
> 2026 history | tail -7
>
Hi Felix,
It looks like Luis already fixed this bug in the more recent versions,
see [0], You could apply it locally to your build and I will add it to
the next release, but it will take some time till I new release from 3.7.
Hauke
[0]:
https://github.com/hauke/compat-drivers/commit/2371a496060c87378c27eb0cb33feeefbc29f2fc
prev parent reply other threads:[~2013-02-12 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40F35DA312B2CC468349B21A177FEE633C8AD5FA@NASANEXD02E.na.qualcomm.com>
2013-02-12 19:35 ` compat-drivers ./driver-select ath9k builds i915 as well, breaks my video Hauke Mehrtens
2013-02-12 20:19 ` Bitterli, Felix
2013-02-12 21:28 ` Hauke Mehrtens [this message]
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=511AB3FD.4020804@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=felixb@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.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 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.