From: stf_xl@wp.pl
To: linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: [PATCH 0/3] wifi: iwlegacy: remove undocumented sysfs files
Date: Tue, 6 Oct 2026 10:14:40 +0200 [thread overview]
Message-ID: <20261006081443.28017-1-stf_xl@wp.pl> (raw)
From: Stanislaw Gruszka <stf_xl@wp.pl>
Remove custom undocumented sysfs files. All are seems unneeded
at this point, except debug_level which is useful for dynamically
change debug mask. That one was moved to debugfs.
Stanislaw Gruszka (3):
wifi: iwlegacy: set debug level using debugfs
wifi: iwlegacy: 4965: remove custom sysfs files
wifi: iwlegacy: 3945: remove custom sysfs files
.../net/wireless/intel/iwlegacy/3945-mac.c | 441 +-----------------
.../net/wireless/intel/iwlegacy/4965-mac.c | 121 -----
drivers/net/wireless/intel/iwlegacy/debug.c | 3 +
3 files changed, 5 insertions(+), 560 deletions(-)
--
2.50.1
next reply other threads:[~2026-10-06 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 8:14 stf_xl [this message]
2026-10-06 8:14 ` [PATCH 1/3] wifi: iwlegacy: set debug level using debugfs stf_xl
2026-10-06 8:14 ` [PATCH 2/3] wifi: iwlegacy: 4965: remove custom sysfs files stf_xl
2026-10-06 8:14 ` [PATCH 3/3] wifi: iwlegacy: 3945: " stf_xl
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=20261006081443.28017-1-stf_xl@wp.pl \
--to=stf_xl@wp.pl \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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