From: Hauke Mehrtens <hauke@hauke-m.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: backports@vger.kernel.org, john@phrozen.org
Subject: Re: [PATCH 06/10] dependencies: make hostap and atmel depend on kernel >= 4.18
Date: Sun, 23 Sep 2018 22:23:57 +0200 [thread overview]
Message-ID: <78f873b0-6053-731a-dfab-37186d262005@hauke-m.de> (raw)
In-Reply-To: <1537733820.1707.10.camel@sipsolutions.net>
[-- Attachment #1.1: Type: text/plain, Size: 897 bytes --]
On 09/23/2018 10:17 PM, Johannes Berg wrote:
> On Sun, 2018-09-23 at 19:45 +0200, Hauke Mehrtens wrote:
>> The hostap and atmel wireless driver now make use of the
>> proc_create_single_data() function which can not easily be backported.
>> As these drivers are not used too often just deactivate them on older
>> kernel versions for now.
>
> It should be pretty easy to backport based on proc_create_data(), which
> has been around since 2.6.26?
>
> johannes
One of the upstream commits is this:
https://git.kernel.org/linus/d51269592c327fcfe8ec80fd169a84f8dc0de73b
The problem is that these function also get some data so we would have
to provide the data and the show function pointer and store it
somewhere. Most of the proc structures are also private so we can not
easily abuse some unused member.
The affected drivers are anyway not used much any more.
Hauke
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-09-24 2:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 17:45 [PATCH 00/10] backports: misc fixes to improve support of 4.19 Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 01/10] backports: Remove ssb and bcma Hauke Mehrtens
2018-09-23 20:10 ` Johannes Berg
2018-09-23 20:18 ` Hauke Mehrtens
2018-09-24 10:48 ` Johannes Berg
2018-09-24 20:17 ` Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 02/10] backports: Remove NFC support Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 03/10] copy: Add crc32poly.h Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 04/10] dependencies: Make RSI_COEX coexistence depend on kernel >= 4.17 Hauke Mehrtens
2018-09-23 20:20 ` Johannes Berg
2018-09-23 17:45 ` [PATCH 05/10] dependencies: Make WIL6210 depend on kernel >= 4.8 Hauke Mehrtens
2018-09-23 20:12 ` Johannes Berg
2018-09-23 20:36 ` Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 06/10] dependencies: make hostap and atmel depend on kernel >= 4.18 Hauke Mehrtens
2018-09-23 20:17 ` Johannes Berg
2018-09-23 20:23 ` Hauke Mehrtens [this message]
2018-09-23 20:33 ` Johannes Berg
2018-09-23 17:45 ` [PATCH 07/10] patches: make mt76 use skb_pad() instead of __skb_pad() Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 08/10] patches: remove .coredump from struct driver for kernel < 4.16 Hauke Mehrtens
2018-09-24 8:36 ` Johannes Berg
2018-09-24 20:20 ` Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 09/10] backports: Make netdev destructor spatch apply correctly again Hauke Mehrtens
2018-09-23 20:17 ` Johannes Berg
2018-09-23 17:45 ` [PATCH 10/10] patches: Do not remove linux/kmemleak.h include Hauke Mehrtens
2018-09-23 20:18 ` Johannes Berg
2018-09-24 8:12 ` [PATCH 00/10] backports: misc fixes to improve support of 4.19 Johannes Berg
2018-09-24 20:27 ` Hauke Mehrtens
2018-09-24 20:28 ` Johannes Berg
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=78f873b0-6053-731a-dfab-37186d262005@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=john@phrozen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).