From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/rtl8821au: add patch fixing sprintf error
Date: Mon, 17 Aug 2020 22:42:51 +0200 [thread overview]
Message-ID: <20200817224251.3e2be53d@gmx.net> (raw)
In-Reply-To: <20200813234209.3b6dd3e1@windsurf.home>
Hello Thomas,
On Thu, 13 Aug 2020 23:42:09 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Thu, 13 Aug 2020 14:31:26 -0700
> Christian Stewart <christian@paral.in> wrote:
>
> > > Applied to master, thanks. I have to say the snippet of code that is
> > > being patched here does not give a very good feel of the rtl8821au
> > > code base :-/
> >
> > After years of struggling with USB rtl cards (and helping others do
> > the same) I have to agree.
>
> And nobody ever thought of taking all these crappy out of tree WiFi
> drivers, submit them for drivers/staging/ inclusion in the upstream
> kernel, and progressively clean them up ?
For some there are already staging alternatives (see [1], [2], [3], [4], [5])...
Regards,
Peter
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/rtl8188eu
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/rtl8192e
[3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/rtl8192u
[4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/rtl8712
[5] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/rtl8723bs
>
> Thomas
next prev parent reply other threads:[~2020-08-17 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 17:38 [Buildroot] [PATCH v2 1/1] package/rtl8821au: add patch fixing sprintf error Christian Stewart
2020-08-13 21:27 ` Thomas Petazzoni
2020-08-13 21:31 ` Christian Stewart
2020-08-13 21:42 ` Thomas Petazzoni
2020-08-17 20:42 ` Peter Seiderer [this message]
2020-08-28 16:29 ` Peter Korsgaard
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=20200817224251.3e2be53d@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox