Changes in .gitignore

ac4f0678 - kbuild: Create intermediate vmlinux build with relocations preserved

Tue, 11 Mar 2025 11:06:20 +0000

kbuild: Create intermediate vmlinux build with relocations preservedThe imperative paradigm used to build vmlinux, extract some info from itor perform some checks on it, and subsequently modify it again goesagainst the declarative paradigm that is usually employed for definingmake rules.In particular, the Makefile.postlink files that consume their input viaan output rule result in some dodgy logic in the decompressor makefilesfor RISC-V and x86, given that the vmlinux.relocs input file needed togenerate the arch-specific relocation tables may not exist or be out ofdate, but cannot be constructed using the ordinary Make dependency basedrules, because the info needs to be extracted while vmlinux is in itsephemeral, non-stripped form.So instead, for architectures that require the static relocations thatare emitted into vmlinux when passing --emit-relocs to the linker, andare subsequently stripped out again, introduce an intermediate vmlinuxtarget called vmlinux.unstripped, and organize the reset of the buildlogic accordingly:- vmlinux.unstripped is created only once, and not updated again- build rules under arch/*/boot can depend on vmlinux.unstripped without running the risk of the data disappearing or being out of date- the final vmlinux generated by the build is not bloated with static relocations that are never needed again after the build completes.Signed-off-by: Ard Biesheuvel Signed-off-by: Masahiro Yamada List of files: /linux-6.15/.gitignore

0730422b - rust: use host dylib naming convention to support macOS

Mon, 16 Dec 2024 15:54:22 +0000

rust: use host dylib naming convention to support macOSBecause the `macros` crate exposes procedural macros, it must becompiled as a dynamic library (so it can be loaded by the compiler atcompile-time).Before this change the resulting artifact was always named`libmacros.so`, which works on hosts where this matches the namingconvention for dynamic libraries. However the proper name on macOS wouldbe `libmacros.dylib`.This turns out to matter even when the dependency is passed with a path(`--extern macros=path/to/libmacros.so` rather than `--extern macros`)because rustc uses the file name to infer the type of the library (seelink). This is because there's no way to specify both the path to andthe type of the external library via CLI flags. The compiler couldspeculatively parse the file to determine its type, but it does not doso today.This means that libraries that match neither rustc's naming conventionfor static libraries nor the platform's naming convention for dynamiclibraries are *rejected*.The only solution I've found is to follow the host platform's namingconvention. This patch does that by querying the compiler to determinethe appropriate name for the artifact. This allows the kernel to buildwith CONFIG_RUST=y on macOS.Link: https://github.com/rust-lang/rust/blob/d829780/compiler/rustc_metadata/src/locator.rs#L728-L752Tested-by: Daniel Gomez Co-developed-by: Fiona Behrens Signed-off-by: Fiona Behrens Signed-off-by: Tamir Duberstein Tested-by: Andreas Hindborg Link: https://lore.kernel.org/r/20241216-b4-dylib-host-macos-v7-1-cfc507681447@gmail.com[ Added `MAKEFLAGS=`s to avoid jobserver warnings. Removed space. Reworded title. - Miguel ]Signed-off-by: Miguel Ojeda List of files: /linux-6.15/.gitignore

4198a4d2 - gitignore: Don't ignore 'tags' directory

Mon, 25 Nov 2024 08:37:36 +0000

gitignore: Don't ignore 'tags' directoryW=1 builds reported warnings regarding files being ignored: tools/testing/selftests/arm64/tags/.gitignore: warning: ignored by one of the .gitignore files tools/testing/selftests/arm64/tags/Makefile: warning: ignored by one of the .gitignore files tools/testing/selftests/arm64/tags/tags_test.c: warning: ignored by one of the .gitignore filesAdjusting the .gitignore entries will prevent these warnings andensure a smoother script execution.Reported-by: kernel test robot Signed-off-by: Li Zhijian Signed-off-by: Masahiro Yamada List of files: /linux-6.15/.gitignore

7d56786e - rust: introduce `.clippy.toml`

Wed, 04 Sep 2024 20:43:39 +0000

rust: introduce `.clippy.toml`Some Clippy lints can be configured/tweaked. We will use these knobs toour advantage in later commits.This is done via a configuration file, `.clippy.toml` [1]. The file iscurrently unstable. This may be a problem in the future, but we can adaptas needed. In addition, we proposed adding Clippy to the Rust CI's RFLjob [2], so we should be able to catch issues pre-merge.Thus introduce the file.Link: https://doc.rust-lang.org/clippy/configuration.html [1]Link: https://github.com/rust-lang/rust/pull/128928 [2]Reviewed-by: Alice Ryhl Reviewed-by: Trevor Gross Tested-by: Gary Guo Reviewed-by: Gary Guo Link: https://lore.kernel.org/r/20240904204347.168520-12-ojeda@kernel.orgSigned-off-by: Miguel Ojeda List of files: /linux-6.15/.gitignore

5f5e7344 - kbuild: generate offset range data for builtin modules

Fri, 06 Sep 2024 14:45:03 +0000

kbuild: generate offset range data for builtin modulesCreate file module.builtin.ranges that can be used to find wherebuilt-in modules are located by their addresses. This will be useful fortracing tools to find what functions are for various built-in modules.The offset range data for builtin modules is generated using: - modules.builtin: associates object files with module names - vmlinux.map: provides load order of sections and offset of first member per section - vmlinux.o.map: provides offset of object file content per section - .*.cmd: build cmd file with KBUILD_MODFILEThe generated data will look like:.text 00000000-00000000 = _text.text 0000baf0-0000cb10 amd_uncore.text 0009bd10-0009c8e0 iosf_mbi....text 00b9f080-00ba011a intel_skl_int3472_discrete.text 00ba0120-00ba03c0 intel_skl_int3472_discrete intel_skl_int3472_tps68470.text 00ba03c0-00ba08d6 intel_skl_int3472_tps68470....data 00000000-00000000 = _sdata.data 0000f020-0000f680 amd_uncoreFor each ELF section, it lists the offset of the first symbol. This canbe used to determine the base address of the section at runtime.Next, it lists (in strict ascending order) offset ranges in that sectionthat cover the symbols of one or more builtin modules. Multiple rangescan apply to a single module, and ranges can be shared between modules.The CONFIG_BUILTIN_MODULE_RANGES option controls whether offset range datais generated for kernel modules that are built into the kernel image.How it works: 1. The modules.builtin file is parsed to obtain a list of built-in module names and their associated object names (the .ko file that the module would be in if it were a loadable module, hereafter referred to as ). This object name can be used to identify objects in the kernel compile because any C or assembler code that ends up into a built-in module will have the option -DKBUILD_MODFILE= present in its build command, and those can be found in the ..cmd file in the kernel build tree. If an object is part of multiple modules, they will all be listed in the KBUILD_MODFILE option argument. This allows us to conclusively determine whether an object in the kernel build belong to any modules, and which. 2. The vmlinux.map is parsed next to determine the base address of each top level section so that all addresses into the section can be turned into offsets. This makes it possible to handle sections getting loaded at different addresses at system boot. We also determine an 'anchor' symbol at the beginning of each section to make it possible to calculate the true base address of a section at runtime (i.e. symbol address - symbol offset). We collect start addresses of sections that are included in the top level section. This is used when vmlinux is linked using vmlinux.o, because in that case, we need to look at the vmlinux.o linker map to know what object a symbol is found in. And finally, we process each symbol that is listed in vmlinux.map (or vmlinux.o.map) based on the following structure: vmlinux linked from vmlinux.a: vmlinux.map: -- might be same as top level section) -- built-in association known -- belongs to module(s) object belongs to ... vmlinux linked from vmlinux.o: vmlinux.map: -- might be same as top level section) vmlinux.o -- need to use vmlinux.o.map -- ignored ... vmlinux.o.map:

-- built-in association known -- belongs to module(s) object belongs to ... 3. As sections, objects, and symbols are processed, offset ranges are constructed in a straight-forward way: - If the symbol belongs to one or more built-in modules: - If we were working on the same module(s), extend the range to include this object - If we were working on another module(s), close that range, and start the new one - If the symbol does not belong to any built-in modules: - If we were working on a module(s) range, close that rangeSigned-off-by: Kris Van Hees Reviewed-by: Nick Alcock Reviewed-by: Alan Maguire Reviewed-by: Steven Rostedt (Google) Tested-by: Sam James Reviewed-by: Sami Tolvanen Tested-by: Sami Tolvanen Signed-off-by: Masahiro Yamada List of files: /linux-6.15/.gitignore

87af9388 - kbuild: remove *.symversions left-over

Sun, 18 Aug 2024 08:37:29 +0000

kbuild: remove *.symversions left-overCommit 5ce2176b81f7 ("genksyms: adjust the output format to modpost")stopped generating *.symversions files.Remove the left-over from the .gitignore file and the 'clean' rule.Signed-off-by: Masahiro Yamada Reviewed-by: Nathan Chancellor List of files: /linux-6.15/.gitignore

76be4f5a - Remove *.orig pattern from .gitignore

Mon, 29 Jul 2024 15:57:38 +0000

Remove *.orig pattern from .gitignoreCommit 3f1b0e1f2875 (".gitignore update") added *.orig and *.rejpatterns to .gitignore in v2.6.23. The commit message didn't give arationale. Later on, commit 1f5d3a6b6532 ("Remove *.rej pattern from.gitignore") removed the *.rej pattern in v2.6.26, on the rationale that*.rej files indicated something went really wrong and should not beignored.The *.rej files are now shown by `git status`, which helps locatedconflicts when applying patches and lowers the probability that theywill go unnoticed. It is however still easy to overlook the *.orig fileswhich slowly polute the source tree. That's not as big of a deal as notnoticing a conflict, but it's still not nice.Drop the *.orig pattern from .gitignore to avoid this and help keep thesource tree clean.Signed-off-by: Laurent Pinchart [masahiroy@kernel.org:I do not have a strong opinion about this. Perhaps some people may havea different opinion.If you are someone who wants to ignore *.orig, it is likely you wouldwant to do so across all projects. Then, $XDG_CONFIG_HOME/git/ignorewould be more suitable for your needs. gitignore(5) suggests, "Patternswhich a user wants Git to ignore in all situations generally go into afile specified by core.excludesFile in the user's ~/.gitconfig".Please note that you cannot do the opposite; if *.orig is ignored bythe project's .gitignore, you cannot override the decision because$XDG_CONFIG_HOME/git/ignore has a lower priority.If *.orig is sitting on the fence, I'd leave it to the users. ]Signed-off-by: Masahiro Yamada List of files: /linux-6.15/.gitignore

a0f6e5e9 - .gitignore: add .gcda files

Tue, 06 Aug 2024 15:38:07 +0000

.gitignore: add .gcda filesThese files contain the runtime coverage data generated by gcov.Signed-off-by: Vegard Nossum Signed-off-by: Chuck Lever Signed-off-by: Allison Henderson Signed-off-by: David S. Miller List of files: /linux-6.15/.gitignore

c8578539 - kbuild: add script and target to generate pacman package

Sat, 20 Jul 2024 09:18:12 +0000

kbuild: add script and target to generate pacman packagepacman is the package manager used by Arch Linux and its derivates.Creating native packages from the kernel tree has multiple advantages:* The package triggers the correct hooks for initramfs generation and bootloader configuration* Uninstallation is complete and also invokes the relevant hooks* New UAPI headers can be installed without any manual bookkeepingThe PKGBUILD file is a modified version of the one used for thedownstream Arch Linux "linux" package.Extra steps that should not be necessary for a development kernel havebeen removed and an UAPI header package has been added.Signed-off-by: Thomas Weißschuh Reviewed-by: Nathan Chancellor Tested-by: Nathan Chancellor Signed-off-by: Masahiro Yamada List of files: /linux-6.15/.gitignore

24507871 - kbuild: create a list of all built DTB files

Tue, 09 Jan 2024 12:07:34 +0000

kbuild: create a list of all built DTB filesIt is useful to have a list of all *.dtb and *.dtbo files generatedfrom the current build.With this commit, 'make dtbs' creates arch/*/boot/dts/dtbs-list, whichlists the dtb(o) files created in the current build. It maintains theorder of the dtb-y additions in Makefiles although the order is notimportant for DTBs. It is a (good) side effect through the reuse of themodules.order rule.Please note this list only includes the files directly added to dtb-y.For example, consider this case: foo-dtbs := foo_base.dtb foo_overlay.dtbo dtb-y := foo.dtbIn this example, the list will include foo.dtb, but not foo_base.dtbor foo_overlay.dtbo.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/.gitignore

5a602de9 - Add .editorconfig file for basic formatting

Thu, 01 Jun 2023 07:53:33 +0000

Add .editorconfig file for basic formattingEditorConfig is a specification to define the most basic code formattingstuff, and it's supported by many editors and IDEs, either directly orvia plugins, including VSCode/VSCodium, Vim, emacs and more.It allows to define formatting style related to indentation, charset,end of lines and trailing whitespaces. It also allows to apply differentformats for different files based on wildcards, so for example it ispossible to apply different configs to *.{c,h}, *.py and *.rs.In linux project, defining a .editorconfig might help to those peoplethat work on different projects with different indentation styles, sothey cannot define a global style. Now they will directly see thecorrect indentation on every fresh clone of the project.See https://editorconfig.orgCo-developed-by: Danny Lin Signed-off-by: Danny Lin Signed-off-by: Íñigo Huguet Acked-by: Mickaël Salaün Reviewed-by: Vincent Mailhol Tested-by: Vincent Mailhol Signed-off-by: Masahiro Yamada List of files: /linux-6.15/.gitignore

ffa46bbc - kbuild: rpm-pkg: generate kernel.spec in rpmbuild/SPECS/

Sat, 30 Sep 2023 10:38:47 +0000

kbuild: rpm-pkg: generate kernel.spec in rpmbuild/SPECS/kernel.spec is the last piece that resides outside the rpmbuild/directory. Move all the RPM-related files to rpmbuild/ consistently.Signed-off-by: Masahiro Yamada Reviewed-by: Nathan Chancellor Tested-by: Nathan Chancellor List of files: /linux-6.15/.gitignore

975667d0 - kbuild: rpm-pkg: rename binkernel.spec to kernel.spec

Sat, 22 Jul 2023 04:48:03 +0000

kbuild: rpm-pkg: rename binkernel.spec to kernel.specNow kernel.spec and binkernel.spec have the exactly same contents.Use kernel.spec for binrpm-pkg as well.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/.gitignore

d5280145 - Revert ".gitignore: ignore .cover and .mbx"

Tue, 04 Jul 2023 22:05:12 +0000

Revert ".gitignore: ignore *.cover and *.mbx"This reverts commit 534066a983df0935847061c844eb178f8a53a9e7.It's actively detrimental in that it hides files that shouldn't behidden.If I have some b4 mbx file in my git directory, it either was alreadyapplied with "git am" and is now stale, or maybe it's waiting for thatto happen. In neither case is "ignore it" the right option.Signed-off-by: Linus Torvalds List of files: /linux-6.15/.gitignore

5e9e95cc - kbuild: implement CONFIG_TRIM_UNUSED_KSYMS without recursion

Sun, 11 Jun 2023 15:50:57 +0000

kbuild: implement CONFIG_TRIM_UNUSED_KSYMS without recursionWhen CONFIG_TRIM_UNUSED_KSYMS is enabled, Kbuild recursively traversesthe directory tree to determine which EXPORT_SYMBOL to trim. If anEXPORT_SYMBOL turns out to be unused by anyone, Kbuild begins thesecond traverse, where some source files are recompiled with theirEXPORT_SYMBOL() tuned into a no-op.Linus stated negative opinions about this slowness in commits: - 5cf0fd591f2e ("Kbuild: disable TRIM_UNUSED_KSYMS option") - a555bdd0c58c ("Kbuild: enable TRIM_UNUSED_KSYMS again, with some guarding")We can do this better now. The final data structures of EXPORT_SYMBOLare generated by the modpost stage, so modpost can selectively emitKSYMTAB entries that are really used by modules.Commit f73edc8951b2 ("kbuild: unify two modpost invocations") is anotherground-work to do this in a one-pass algorithm. With the list of modules,modpost sets sym->used if it is used by a module. modpost emits KSYMTABonly for symbols with sym->used==true.BTW, Nicolas explained why the trimming was implemented with recursion: https://lore.kernel.org/all/2o2rpn97-79nq-p7s2-nq5-8p83391473r@syhkavp.arg/Actually, we never achieved that level of optimization where the chainreaction of trimming comes into play because: - CONFIG_LTO_CLANG cannot remove any unused symbols - CONFIG_LD_DEAD_CODE_DATA_ELIMINATION is enabled only for vmlinux, but not modulesIf deeper trimming is required, we need to revisit this, but I guessthat is unlikely to happen.Signed-off-by: Masahiro Yamada List of files: /linux-6.15/.gitignore

2bc42f48 - .gitignore: Do not ignore .kunitconfig files

Mon, 17 Apr 2023 14:32:19 +0000

.gitignore: Do not ignore .kunitconfig filesCircumvent the .gitignore wildcard to avoid warnings about ignored.kunitconfig files. As far as I can tell, the warnings are harmlessand these files are not actually ignored.Reported-by: kernel test robot Link: https://lore.kernel.org/oe-kbuild-all/202304142337.jc4oUrov-lkp@intel.com/Signed-off-by: Chuck Lever Signed-off-by: Jakub Kicinski List of files: /linux-6.15/.gitignore

cb8865fd - .gitignore: Unignore .kunitconfig

Fri, 27 Jan 2023 14:57:08 +0000

.gitignore: Unignore .kunitconfigThere are almost dozen of .kunitconfig files that are ignored buttracked. Unignore them.Signed-off-by: Andy Shevchenko Reviewed-by: David Gow Signed-off-by: Shuah Khan List of files: /linux-6.15/.gitignore

81f59a26 - kbuild: rpm-pkg: move source components to rpmbuild/SOURCES

Wed, 15 Mar 2023 15:50:17 +0000

kbuild: rpm-pkg: move source components to rpmbuild/SOURCESPrepare to add more files to the source RPM.Also, fix the build error when KCONFIG_CONFIG is set: error: Bad file: ./.config: No such file or directorySigned-off-by: Masahiro Yamada List of files: /linux-6.15/.gitignore

534066a9 - .gitignore: ignore .cover and .mbx

Mon, 30 Jan 2023 08:28:49 +0000

.gitignore: ignore *.cover and *.mbxThe 'b4' command creates a *.mbx file, and also a *.cover file if thepatch set has a cover-letter. Ignore them.Signed-off-by: Masahiro Yamada Reviewed-by: Nicolas Schier Reviewed-by: Nick Desaulniers List of files: /linux-6.15/.gitignore

b8a9ddca - .gitignore: update the command to check tracked files being ignored

Thu, 29 Dec 2022 07:43:09 +0000

.gitignore: update the command to check tracked files being ignoredRecent git versions do not accept the noted command. $ git ls-files -i --exclude-standard fatal: ls-files -i must be used with either -o or -cThe -c was implied before, but we need to make it explicit sincegit commit b338e9f66873 ("ls-files: error out on -i unless -o or -care specified").Also, replace --exclude-standard with --exclude-per-directory=.gitignoreso that everyone will get consistent results.git-ls-files(1) says: --exclude-standard Add the standard Git exclusions: .git/info/exclude, .gitignore in each directory, and the user's global exclusion file.We cannot predict what is locally added to .git/info/exclude or theuser's global exclusion file.We can only manage .gitignore files committed to the repository.Signed-off-by: Masahiro Yamada Reviewed-by: Miguel Ojeda List of files: /linux-6.15/.gitignore