Intel official release 1.0.11#27
Merged
Merged
Conversation
On kernels with PASID kAPI patches, iommufd supports PASID-based DMA passthrough via the IOMMUFD_BIND_FLAGS_PASID enum value in include/linux/iommufd.h. Define a new HAVE_IOMMUFD_BIND_PASID macro when the enum value is found, allowing driver code to select the iommufd kAPI path. Signed-off-by: Yahui Cao <yahui.cao@intel.com>
mul_u64_u64_div_u64_roundup()") changed mul_u64_u64_div_u64 from function to a macro. Adjust the logic in kcompat generator to accomodate this change.
SLES 16.1 defines __counted_by in a different header, resulting in compat implementation redefining the original implementation. Add this header to check against. Signed-off-by: Marcin Szycik <marcin.szycik@intel.com> Change-type: Other
around the pound (#), as it is the case for SLES 6.1 Signed-off-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
config") introduced ndo_hwtstamp_get and ndo_hwtstamp_set callbacks in legacy way to get/set HW timestamp config") removed the legacy fallback from ndo_eth_ioctl for SIOCGHWTSTAMP/SIOCSHWTSTAMP. Add detection of ndo_hwtstamp_get in net_device_ops to define HAVE_NDO_HWTSTAMP, allowing drivers to register the new callbacks and maintain hwtstamp support on kernels >= 6.15. Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com> Change-type: Other
Move HAVE_NDO_HWTSTAMP detection line to its correct alphabetical position after HAVE_NDO_GET_TSTAMP and before HAVE_NDO_SETUP_TC_*. This fixes the kcompat-generator-linter sort order check. Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com> Change-type: Other
Some of our test environments compile the driver with unused parameter warnings enabled. The no-op XDP functions added by commit 4d3bfa031d1d parameters as unused, resulting in warnings being triggered in CI. Explicitely mark the parameters for these empty functions as unused in order to silence the spurious compiler warnings. Change-type: Other Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Several files in COMPAT were missing an SPDX license identifier. Add
- C/header files get `/* SPDX-License-Identifier: GPL-2.0 */`.
- Shell and awk scripts get `# SPDX-License-Identifier: GPL-2.0`
after the shebang line.
- The Sphinx Documentation Makefile gets `# SPDX-License-Identifier:
GPL-2.0` prepended.
No Intel copyright lines are added, since these are mostly tooling
and test helpers rather than newly-authored driver code.
Change-type: Other
Signed-off-by: Sarath Somasekharan <sarath.somasekharan@intel.com>
On openEuler-22.03,the script check_aux_bus returns exit_need_oot_auxiliary because the definition CONFIG_AUXILIARY_BUS is not detected.But some auxiliary bus code are included in the kernel, while the CONFIG_AUXILIARY_BUS is not defined in the autoconf.h file since no driver selects this module, meaning it may be not mature enough. Hence,the ice driver thinks OOT auxiliary bus module is needed, and part of auxiliary bus code is defined in-kernel and OOT simultaneously, which leads to the redefinition error. By checking the flag HAVE_AUXILIARY_DEVICE_ID to decide whether the part in kernel or OOT is used. Meanwhile, change AUXILIARY_NAME_SIZE from 38 to 32 so that it's compatible with the upstream. Bump auxiliary version too. Change-type:ImplementationChange Signed-off-by: Michael Jin <Michael.Jin@intel.com>
Currently auxiliary_compat.h and auxiliary_bus.h are included separately. It makes sense to include the kcompat stuff auxiliary_compat.h for auxiliary module in the auxiliary_bus.h. With this, commit 5f21c54567b8 kcompat macro HAVE_AUXILIARY_DEVICE_ID correctly. Otherwise, auxiliary_bus.h will rely on auxiliary_compat.h. However, if doing so, it will result in redefinitions for the functions which are defined in both auxiliary_compat.h and kcompat.h. Currently auxiliary_compat.h is actually a minimum part of kcompat.h, The idea here is to include the minimum par auxiliary_compat.h into kcompat.h to avoid the duplicated pieces of code in both files. This way, the functions redefinition can be fixed. Once auxiliary_compat.h is included in kcompat.h, it forces non-auxiliary bus drivers to include auxiliary bus submodule as indicated by Jake. This change moves the auxiliary_compat.h to compat repo, and doesn't rename it to kcompat_auxiliary.h since it requires other driver changes Change-type:ImplementationChange Signed-off-by: Michael Jin <Michael.Jin@intel.com>
Two ARM 4.19 legacy build failures introduced by commit 03ae5f5c
mismatch.
The auxiliary_compat.h macro that maps bus_find_device() to
_kc_bus_find_device() on kernels with the old non-const prototype
was not in scope at the call site. Before the submodule bump,
auxiliary.c had its own explicit #include "auxiliary_compat.h"
line, which guaranteed the override regardless of which
<linux/auxiliary_bus.h> won the -I search. The bump removed that
line and relies on auxiliary_bus.h to pull auxiliary_compat.h in
transitively. When the build kernel ships its own backported
<linux/auxiliary_bus.h> (e.g. /usr/src/kernels/linux-4.19.56 on
the Jenkins ARM legacy runner), kbuild's -I${KSRC}/include wins
over -I${STAGE_DIR}, the staged OOT auxiliary_bus.h is bypassed,
and auxiliary_compat.h is never pulled in. The bus_find_device()
call then resolves to the kernel's non-const prototype and fails
to compile.
Restore the pre-bump behaviour at staging time by sed-injecting an
explicit #include "auxiliary_compat.h" into _auxiliary.c right
after the auxiliary_bus.h include. The auxiliary_compat.h sibling
lives in the same directory as _auxiliary.c, so a plain quoted
include always resolves locally. The AUXILIARY submodule is left
untouched.
only referenced inside #ifdef CONFIG_EDT && HAVE_ETF_SUPPORT
blocks. On ARM 4.19 both flags are off, the variable is unused,
and -Werror=unused-variable fails the build. Mark it
__maybe_unused.
Change-type: Other
Signed-off-by: Madhu Chittim <madhu.chittim@intel.com>
Bump version for 3.0 Release. Change-type: EngineeringNotes Signed-off-by: Madhu Chittim <madhu.chittim@intel.com>
madhuchittim
approved these changes
May 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the IDPF release 1.0.11
with incremental linear git history.
Signed-off-by: Sarath Somasekharan sarath.somasekharan@intel.com