emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#45362: closed ([PATCH 0/1] rtl8812au-aircrack-ng won't build on Linu


From: GNU bug Tracking System
Subject: bug#45362: closed ([PATCH 0/1] rtl8812au-aircrack-ng won't build on Linux 5.10)
Date: Tue, 22 Dec 2020 12:36:03 +0000

Your message dated Tue, 22 Dec 2020 13:35:10 +0100
with message-id <877dpaauip.fsf@nckx>
and subject line Re: [bug#45362] [PATCH 0/1] rtl8812au-aircrack-ng won't build 
on Linux 5.10
has caused the debbugs.gnu.org bug report #45362,
regarding [PATCH 0/1] rtl8812au-aircrack-ng won't build on Linux 5.10
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
45362: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=45362
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH 0/1] rtl8812au-aircrack-ng won't build on Linux 5.10 Date: Tue, 22 Dec 2020 13:46:50 +0300
Hello!  I'm using and recently it stopped building succesfully.
Probably due to kernel update I'm not too sure.

Fix for this was just merged today:
https://github.com/aircrack-ng/rtl8812au/pull/791

I haven't tested it on kernell versions defined in linux.scm.  Do I need to do
it before submitting patch for linux module?

David Dashyan (1):
  rtl8812au-aircrack-ng-linux-module: Update to 62cb003

 gnu/packages/linux.scm | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)


base-commit: 2e7c2dc8fa64442eb5b67670c5533090bebdd7fd
-- 
2.29.2




--- End Message ---
--- Begin Message --- Subject: Re: [bug#45362] [PATCH 0/1] rtl8812au-aircrack-ng won't build on Linux 5.10 Date: Tue, 22 Dec 2020 13:35:10 +0100
David,

David Dashyan 写道:
Probably due to kernel update I'm not too sure.

Hah, yes :-) Same damn upstream change that kept me busy all morning.

Fix for this was just merged today:
https://github.com/aircrack-ng/rtl8812au/pull/791

At a glance that looks like it should keep working fine on older kernels.

I haven't tested it on kernell versions defined in linux.scm. Do I need to do
it before submitting patch for linux module?

I would, at least the latest ‘longterm’ release, currently 5.4. In this case it built fine.

The project obviously intend to keep backwards compatibility so any regressions are theirs to fix & ours to update or patch to.

Pushed with our conventional commit message, please take a look[0].

Thanks!

T G-R

[0]: https://git.savannah.gnu.org/cgit/guix.git/commit/?id=8c66ac72fb0ad01227f196d61a0a7675b6f48d61

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]