Changes in Makefile

3a1d429e - wifi: wext/libipw: move spy implementation to libipw

Mon, 07 Oct 2024 19:02:53 +0000

wifi: wext/libipw: move spy implementation to libipwThere's no driver left using this other than ipw2200,so move the data bookkeeping and code into libipw.Link: https://patch.msgid.link/20241007210254.037d864cda7d.Ib2197cb056ff05746d3521a5fba637062acb7314@changeidSigned-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

02f220b5 - wifi: ipw2x00/lib80211: move remaining lib80211 into libipw

Mon, 07 Oct 2024 18:26:55 +0000

wifi: ipw2x00/lib80211: move remaining lib80211 into libipwThere's already much code in libipw that used to be sharedwith more drivers, but now with the prior cleanups, those oldIntel ipw2x00 drivers are also the only ones using whatever isnow left of lib80211. Move lib80211 entirely into libipw.Link: https://patch.msgid.link/20241007202707.915ef7b9e7c7.Ib9876d2fe3c90f11d6df458b16d0b7d4bf551a8d@changeidSigned-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

b1992c37 - kbuild: use $(src) instead of $(srctree)/$(src) for source directory

Sat, 27 Apr 2024 14:55:02 +0000

kbuild: use $(src) instead of $(srctree)/$(src) for source directoryKbuild conventionally uses $(obj)/ for generated files, and $(src)/ forchecked-in source files. It is merely a convention without any functionaldifference. In fact, $(obj) and $(src) are exactly the same, as definedin scripts/Makefile.build: src := $(obj)When the kernel is built in a separate output directory, $(src) doesnot accurately reflect the source directory location. While Kbuildresolves this discrepancy by specifying VPATH=$(srctree) to search forsource files, it does not cover all cases. For example, when adding aheader search path for local headers, -I$(srctree)/$(src) is typicallypassed to the compiler.This introduces inconsistency between upstream and downstream Makefilesbecause $(src) is used instead of $(srctree)/$(src) for the latter.To address this inconsistency, this commit changes the semantics of$(src) so that it always points to the directory in the source tree.Going forward, the variables used in Makefiles will have the followingmeanings: $(obj) - directory in the object tree $(src) - directory in the source tree (changed by this commit) $(objtree) - the top of the kernel object tree $(srctree) - the top of the kernel source treeConsequently, $(srctree)/$(src) in upstream Makefiles need to be replacedwith $(src).Signed-off-by: Masahiro Yamada Reviewed-by: Nicolas Schier List of files: /linux-6.15/net/wireless/Makefile

bf6b980f - wifi: cfg80211: sort certificates in build

Thu, 14 Dec 2023 11:03:49 +0000

wifi: cfg80211: sort certificates in buildThe build can become unreproducible if the list of filesfound by $(wildcard ...) differs. Sort the list to avoidthis.Signed-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

730eeb17 - wifi: cfg80211: add first kunit tests, for element defrag

Sun, 27 Aug 2023 11:05:20 +0000

wifi: cfg80211: add first kunit tests, for element defragAdd a couple of tests for element defragmentation, tosee that the function works correctly.Signed-off-by: Johannes Berg Signed-off-by: Gregory Greenman Link: https://lore.kernel.org/r/20230827135854.e2a5cead1816.I09f0edc19d162b54ee330991c728c1e9aa42ebf6@changeidSigned-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

a12f7634 - cfg80211: fix CONFIG_CFG80211_EXTRA_REGDB_KEYDIR typo

Mon, 21 Feb 2022 14:55:12 +0000

cfg80211: fix CONFIG_CFG80211_EXTRA_REGDB_KEYDIR typoThe kbuild change here accidentally removed not only theunquoting, but also the last character of the variablename. Fix that.Fixes: 129ab0d2d9f3 ("kbuild: do not quote string values in include/config/auto.conf")Reviewed-by: Masahiro Yamada Link: https://lore.kernel.org/r/20220221155512.1d25895f7c5f.I50fa3d4189fcab90a2896fe8cae215035dae9508@changeidSigned-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

129ab0d2 - kbuild: do not quote string values in include/config/auto.conf

Tue, 14 Dec 2021 02:53:53 +0000

kbuild: do not quote string values in include/config/auto.confThe previous commit fixed up all shell scripts to not includeinclude/config/auto.conf.Now that include/config/auto.conf is only included by Makefiles,we can change it into a more Make-friendly form.Previously, Kconfig output string values enclosed with double-quotes(both in the .config and include/config/auto.conf): CONFIG_X="foo bar"Unlike shell, Make handles double-quotes (and single-quotes as well)verbatim. We must rip them off when used.There are some patterns: [1] $(patsubst "%",%,$(CONFIG_X)) [2] $(CONFIG_X:"%"=%) [3] $(subst ",,$(CONFIG_X)) [4] $(shell echo $(CONFIG_X))These are not only ugly, but also fragile.[1] and [2] do not work if the value contains spaces, like CONFIG_X=" foo bar "[3] does not work correctly if the value contains double-quotes like CONFIG_X="foo\"bar"[4] seems to work better, but has a cost of forking a process.Anyway, quoted strings were always PITA for our Makefiles.This commit changes Kconfig to stop quoting in include/config/auto.conf.These are the string type symbols referenced in Makefiles or scripts: ACPI_CUSTOM_DSDT_FILE ARC_BUILTIN_DTB_NAME ARC_TUNE_MCPU BUILTIN_DTB_SOURCE CC_IMPLICIT_FALLTHROUGH CC_VERSION_TEXT CFG80211_EXTRA_REGDB_KEYDIR EXTRA_FIRMWARE EXTRA_FIRMWARE_DIR EXTRA_TARGETS H8300_BUILTIN_DTB INITRAMFS_SOURCE LOCALVERSION MODULE_SIG_HASH MODULE_SIG_KEY NDS32_BUILTIN_DTB NIOS2_DTB_SOURCE OPENRISC_BUILTIN_DTB SOC_CANAAN_K210_DTB_SOURCE SYSTEM_BLACKLIST_HASH_LIST SYSTEM_REVOCATION_KEYS SYSTEM_TRUSTED_KEYS TARGET_CPU UNUSED_KSYMS_WHITELIST XILINX_MICROBLAZE0_FAMILY XILINX_MICROBLAZE0_HW_VER XTENSA_VARIANT_NAMEI checked them one by one, and fixed up the code where necessary.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/net/wireless/Makefile

3df15f34 - cfg80211: honour V=1 in certificate code generation

Fri, 27 Aug 2021 11:11:12 +0000

cfg80211: honour V=1 in certificate code generationWhen we generate the code for built-in certificates, honourthe V=1 build option to print out the script doing it.Signed-off-by: Johannes Berg Link: https://lore.kernel.org/r/20210827131112.dc5492458d55.Idefe4ce8f9681a5ad576d3c6e57c7bff142244de@changeidSigned-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

b5642479 - cfg80211: make certificate generation more robust

Fri, 18 Jun 2021 10:41:29 +0000

cfg80211: make certificate generation more robustIf all net/wireless/certs/*.hex files are deleted, the buildwill hang at this point since the 'cat' command will have noarguments. Do "echo | cat - ..." so that even if the "..."part is empty, the whole thing won't hang.Cc: stable@vger.kernel.orgSigned-off-by: Johannes Berg Signed-off-by: Luca Coelho Link: https://lore.kernel.org/r/iwlwifi.20210618133832.c989056c3664.Ic3b77531d00b30b26dcd69c64e55ae2f60c3f31e@changeidSigned-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

32b5a2c9 - wireless: Skip directory when generating certificates

Tue, 07 May 2019 17:28:15 +0000

wireless: Skip directory when generating certificatesCommit 715a12334764 ("wireless: don't write C files on failures") dropsthe `test -f $$f` check. The list of targets contains theCONFIG_CFG80211_EXTRA_REGDB_KEYDIR directory itself, and this check usedto filter it out. After the check was removed, the extra keydir optionno longer works, failing with the following message:od: 'standard input': read error: Is a directoryThis commit restores the check to make extra keydir work again.Fixes: 715a12334764 ("wireless: don't write C files on failures")Signed-off-by: Maxim Mikityanskiy Signed-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

9bb7e0f2 - cfg80211: add peer measurement with FTM initiator API

Mon, 10 Sep 2018 11:29:12 +0000

cfg80211: add peer measurement with FTM initiator APIAdd a new "peer measurement" API, that can be used to measurecertain things related to a peer. Right now, only implementFTM (flight time measurement) over it, but the idea is thatit'll be extensible to also support measuring the necessarythings to calculate e.g. angle-of-arrival for WiGig.The API is structured to have a generic list of peers andchannels to measure with/on, and then for each of those aset of measurements (again, only FTM right now) to perform.Results are sent to the requesting socket, including a finalcomplete message.Closing the controlling netlink socket will abort a runningmeasurement.v3: - add a bit to report "final" for partial results - remove list keeping etc. and just unicast out the results to the requester (big code reduction ...) - also send complete message unicast, and as a result remove the multicast group - separate out struct cfg80211_pmsr_ftm_request_peer from struct cfg80211_pmsr_request_peer - document timeout == 0 if no timeout - disallow setting timeout nl80211 attribute to 0, must not include attribute for no timeout - make MAC address randomization optional - change num bursts exponent default to 0 (1 burst, rather rather than the old default of 15==don't care)v4: - clarify NL80211_ATTR_TIMEOUT documentationv5: - remove unnecessary nl80211 multicast/family changes - remove partial results bit/flag, final is sufficient - add max_bursts_exponent, max_ftms_per_burst to capability - rename "frames per burst" -> "FTMs per burst"v6: - rename cfg80211_pmsr_free_wdev() to cfg80211_pmsr_wdev_down() and call it in leave, so the device can't go down with any pending measurementsv7: - wording fixes (Lior) - fix ftm.max_bursts_exponent to allow having the limit of 0 (Lior)v8: - copyright statements - minor coding style fixes - fix error path leakSigned-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

04a7279f - cfg80211: ship certificates as hex files

Tue, 19 Dec 2017 08:26:17 +0000

cfg80211: ship certificates as hex filesNot only does this remove the need for the hexdump code in mostnormal kernel builds (still there for the extra directory), butit also removes the need to ship binary files, which apparentlyis somewhat problematic, as Randy reported.While at it, also add the generated files to clean-files.Reported-by: Randy Dunlap Signed-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

5d324073 - cfg80211: always rewrite generated files from scratch

Thu, 14 Dec 2017 13:33:38 +0000

cfg80211: always rewrite generated files from scratchCurrently the certs C code generation appends to the generated files,which is most likely a leftover from commit 715a12334764 ("wireless:don't write C files on failures"). This causes duplicate code in thegenerated files if the certificates have their timestamps modifiedbetween builds and thereby trigger the generation rules.Fixes: 715a12334764 ("wireless: don't write C files on failures")Signed-off-by: Thierry Reding Signed-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

715a1233 - wireless: don't write C files on failures

Tue, 05 Dec 2017 10:59:33 +0000

wireless: don't write C files on failuresChange the scripting inside the shipped/extra certs C codegeneration to not write the file when there are any failures.That way, if the build aborts due to failures, we don't getinto a situation where a dummy file has been created and thenext build succeeds, but not with the desired output.Fixes: 90a53e4432b1 ("cfg80211: implement regdb signature checking")Signed-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

71334963 - wireless: replace usage of hexdump with od/sed

Tue, 05 Dec 2017 10:27:59 +0000

wireless: replace usage of hexdump with od/sedSince od/sed are in posix, hopefully there's a better chancepeople will have them, over hexdump.Fixes: 90a53e4432b1 ("cfg80211: implement regdb signature checking")Signed-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/net/wireless/Makefile

1188e2a9 - cfg80211: don't print log output for building shipped-certs

Fri, 13 Oct 2017 12:04:30 +0000

cfg80211: don't print log output for building shipped-certsBuilding an allmodconfig kernel with 'make -s' now prints a single line: GEN net/wireless/shipped-certs.cUsing '$(kecho)' here will skip the output with 'make -s' butotherwise keeps printing it, which is consistent with how wehandle all the other output.Fixes: 90a53e4432b1 ("cfg80211: implement regdb signature checking")Signed-off-by: Arnd Bergmann Signed-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

90a53e44 - cfg80211: implement regdb signature checking

Wed, 13 Sep 2017 20:21:08 +0000

cfg80211: implement regdb signature checkingCurrently CRDA implements the signature checking, and the previouscommits added the ability to load the whole regulatory databaseinto the kernel.However, we really can't lose the signature checking, so implementit in the kernel by loading a detached signature (regulatory.db.p7s)and check it against built-in keys.Signed-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

c8c240e2 - cfg80211: reg: remove support for built-in regdb

Thu, 15 Oct 2015 12:35:41 +0000

cfg80211: reg: remove support for built-in regdbParsing and building C structures from a regdb is no longer neededsince the "firmware" file (regulatory.db) can be linked into thekernel image to achieve the same effect.Signed-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile

e691ac2f - cfg80211: support ieee80211-freq-limit DT property

Wed, 04 Jan 2017 17:58:31 +0000

cfg80211: support ieee80211-freq-limit DT propertyThis patch adds a helper for reading that new property and applyinglimitations of supported channels specified this way.It is used with devices that normally support a wide wireless band butin a given config are limited to some part of it (usually due to boarddesign). For example a dual-band chipset may be able to support one bandonly because of used antennas.It's also common that tri-band routers have separated radios for lowerand higher part of 5 GHz band and it may be impossible to say which iswhich without a DT info.Signed-off-by: Rafał Miłecki [add new function to documentation, fix link]Signed-off-by: Johannes Berg List of files: /linux-6.15/net/wireless/Makefile