From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: David Dashyan <mail@davie.li>
Cc: 45362-done@debbugs.gnu.org, guix-patches@gnu.org
Subject: bug#45362: [PATCH 0/1] rtl8812au-aircrack-ng won't build on Linux 5.10
Date: Tue, 22 Dec 2020 13:35:10 +0100 [thread overview]
Message-ID: <877dpaauip.fsf@nckx> (raw)
In-Reply-To: <20201222104650.11799-1-mail@davie.li>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-12-22 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 10:46 [bug#45362] [PATCH 0/1] rtl8812au-aircrack-ng won't build on Linux 5.10 David Dashyan
2020-12-22 10:51 ` [bug#45362] [PATCH 1/1] rtl8812au-aircrack-ng-linux-module: Update to 62cb003 David Dashyan
2020-12-22 11:00 ` [bug#45362] [PATCH 0/1] rtl8812au-aircrack-ng won't build on Linux 5.10 David Dashyan
2020-12-22 12:35 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-12-22 17:50 ` David Dashyan
2020-12-22 20:36 ` Tobias Geerinckx-Rice via Guix-patches via
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=877dpaauip.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=45362-done@debbugs.gnu.org \
--cc=mail@davie.li \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.