Changes in Makefile

1ac731c529cd4d6adbce134754b51ff7d822b145 - Merge branch 'next' into for-linus

Thu, 31 Aug 2023 01:06:38 +0200

Merge branch 'next' into for-linusPrepare input updates for 6.6 merge window. List of files: /linux/drivers/net/vxlan/Makefile

50501936288d6a29d7ef78f25d00e33240fad45f - Merge tag 'v6.4' into next

Mon, 17 Jul 2023 18:20:46 +0200

Merge tag 'v6.4' into nextSync up with mainline to bring in updates to shared infrastructure. List of files: /linux/drivers/net/vxlan/Makefile

db6da59cf27b5661ced03754ae0550f8914eda9e - Merge drm/drm-next into drm-misc-next-fixes

Thu, 15 Jun 2023 10:34:19 +0200

Merge drm/drm-next into drm-misc-next-fixesBackmerging to sync drm-misc-next-fixes with drm-misc-next.Signed-off-by: Thomas Zimmermann List of files: /linux/drivers/net/vxlan/Makefile

03c601927b673a243c9595e1ecc9e8adfdd02438 - Merge branch 'drm-next' of git://anongit.freedesktop.org/drm/drm into msm-next-lumag-base

Mon, 12 Jun 2023 23:20:40 +0200

Merge branch 'drm-next' of git://anongit.freedesktop.org/drm/drm into msm-next-lumag-baseMerge the drm-next tree to pick up the DRM DSC helpers (merged viadrm-intel-next tree). MSM DSC v1.2 patches depend on these helpers.Signed-off-by: Dmitry Baryshkov List of files: /linux/drivers/net/vxlan/Makefile

9ff17e6bdaa50892dd9bdb1b116cb71b73dd711a - Merge drm/drm-next into drm-intel-gt-next

Mon, 05 Jun 2023 12:10:23 +0200

Merge drm/drm-next into drm-intel-gt-nextFor conflict avoidance we need the following commit: c9a9f18d3ad8 drm/i915/huc: use const struct bus_type pointersSigned-off-by: Tvrtko Ursulin List of files: /linux/drivers/net/vxlan/Makefile

9c3a985f88fa4de82bf4bda906095ce6444e9039 - Merge drm/drm-next into drm-intel-next

Wed, 17 May 2023 15:30:24 +0200

Merge drm/drm-next into drm-intel-nextBackmerge to get some hwmon dependencies.Signed-off-by: Rodrigo Vivi List of files: /linux/drivers/net/vxlan/Makefile

50282fd57bcd3525c9d81eef58df8718e4337c6d - Merge drm/drm-fixes into drm-misc-fixes

Fri, 12 May 2023 09:47:12 +0200

Merge drm/drm-fixes into drm-misc-fixesLet's bring 6.4-rc1 in drm-misc-fixes to start the new fix cycle.Signed-off-by: Maxime Ripard List of files: /linux/drivers/net/vxlan/Makefile

ff32fcca64437f679a2bf1c0a19d5def389a18e2 - Merge drm/drm-next into drm-misc-next

Tue, 09 May 2023 15:03:40 +0200

Merge drm/drm-next into drm-misc-nextStart the 6.5 release cycle.Signed-off-by: Maxime Ripard List of files: /linux/drivers/net/vxlan/Makefile

6e98b09da931a00bf4e0477d0fa52748bf28fcce - Merge tag 'net-next-6.4' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next

Thu, 27 Apr 2023 01:07:23 +0200

Merge tag 'net-next-6.4' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-nextPull networking updates from Paolo Abeni: "Core: - Introduce a config option to tweak MAX_SKB_FRAGS. Increasing the default value allows for better BIG TCP performances - Reduce compound page head access for zero-copy data transfers - RPS/RFS improvements, avoiding unneeded NET_RX_SOFTIRQ when possible - Threaded NAPI improvements, adding defer skb free support and unneeded softirq avoidance - Address dst_entry reference count scalability issues, via false sharing avoidance and optimize refcount tracking - Add lockless accesses annotation to sk_err[_soft] - Optimize again the skb struct layout - Extends the skb drop reasons to make it usable by multiple subsystems - Better const qualifier awareness for socket casts BPF: - Add skb and XDP typed dynptrs which allow BPF programs for more ergonomic and less brittle iteration through data and variable-sized accesses - Add a new BPF netfilter program type and minimal support to hook BPF programs to netfilter hooks such as prerouting or forward - Add more precise memory usage reporting for all BPF map types - Adds support for using {FOU,GUE} encap with an ipip device operating in collect_md mode and add a set of BPF kfuncs for controlling encap params - Allow BPF programs to detect at load time whether a particular kfunc exists or not, and also add support for this in light skeleton - Bigger batch of BPF verifier improvements to prepare for upcoming BPF open-coded iterators allowing for less restrictive looping capabilities - Rework RCU enforcement in the verifier, add kptr_rcu and enforce BPF programs to NULL-check before passing such pointers into kfunc - Add support for kptrs in percpu hashmaps, percpu LRU hashmaps and in local storage maps - Enable RCU semantics for task BPF kptrs and allow referenced kptr tasks to be stored in BPF maps - Add support for refcounted local kptrs to the verifier for allowing shared ownership, useful for adding a node to both the BPF list and rbtree - Add BPF verifier support for ST instructions in convert_ctx_access() which will help new -mcpu=v4 clang flag to start emitting them - Add ARM32 USDT support to libbpf - Improve bpftool's visual program dump which produces the control flow graph in a DOT format by adding C source inline annotations Protocols: - IPv4: Allow adding to IPv4 address a 'protocol' tag. Such value indicates the provenance of the IP address - IPv6: optimize route lookup, dropping unneeded R/W lock acquisition - Add the handshake upcall mechanism, allowing the user-space to implement generic TLS handshake on kernel's behalf - Bridge: support per-{Port, VLAN} neighbor suppression, increasing resilience to nodes failures - SCTP: add support for Fair Capacity and Weighted Fair Queueing schedulers - MPTCP: delay first subflow allocation up to its first usage. This will allow for later better LSM interaction - xfrm: Remove inner/outer modes from input/output path. These are not needed anymore - WiFi: - reduced neighbor report (RNR) handling for AP mode - HW timestamping support - support for randomized auth/deauth TA for PASN privacy - per-link debugfs for multi-link - TC offload support for mac80211 drivers - mac80211 mesh fast-xmit and fast-rx support - enable Wi-Fi 7 (EHT) mesh support Netfilter: - Add nf_tables 'brouting' support, to force a packet to be routed instead of being bridged - Update bridge netfilter and ovs conntrack helpers to handle IPv6 Jumbo packets properly, i.e. fetch the packet length from hop-by-hop extension header. This is needed for BIT TCP support - The iptables 32bit compat interface isn't compiled in by default anymore - Move ip(6)tables builtin icmp matches to the udptcp one. This has the advantage that icmp/icmpv6 match doesn't load the iptables/ip6tables modules anymore when iptables-nft is used - Extended netlink error report for netdevice in flowtables and netdev/chains. Allow for incrementally add/delete devices to netdev basechain. Allow to create netdev chain without device Driver API: - Remove redundant Device Control Error Reporting Enable, as PCI core has already error reporting enabled at enumeration time - Move Multicast DB netlink handlers to core, allowing devices other then bridge to use them - Allow the page_pool to directly recycle the pages from safely localized NAPI - Implement lockless TX queue stop/wake combo macros, allowing for further code de-duplication and sanitization - Add YNL support for user headers and struct attrs - Add partial YNL specification for devlink - Add partial YNL specification for ethtool - Add tc-mqprio and tc-taprio support for preemptible traffic classes - Add tx push buf len param to ethtool, specifies the maximum number of bytes of a transmitted packet a driver can push directly to the underlying device - Add basic LED support for switch/phy - Add NAPI documentation, stop relaying on external links - Convert dsa_master_ioctl() to netdev notifier. This is a preparatory work to make the hardware timestamping layer selectable by user space - Add transceiver support and improve the error messages for CAN-FD controllers New hardware / drivers: - Ethernet: - AMD/Pensando core device support - MediaTek MT7981 SoC - MediaTek MT7988 SoC - Broadcom BCM53134 embedded switch - Texas Instruments CPSW9G ethernet switch - Qualcomm EMAC3 DWMAC ethernet - StarFive JH7110 SoC - NXP CBTX ethernet PHY - WiFi: - Apple M1 Pro/Max devices - RealTek rtl8710bu/rtl8188gu - RealTek rtl8822bs, rtl8822cs and rtl8821cs SDIO chipset - Bluetooth: - Realtek RTL8821CS, RTL8851B, RTL8852BS - Mediatek MT7663, MT7922 - NXP w8997 - Actions Semi ATS2851 - QTI WCN6855 - Marvell 88W8997 - Can: - STMicroelectronics bxcan stm32f429 Drivers: - Ethernet NICs: - Intel (1G, icg): - add tracking and reporting of QBV config errors - add support for configuring max SDU for each Tx queue - Intel (100G, ice): - refactor mailbox overflow detection to support Scalable IOV - GNSS interface optimization - Intel (i40e): - support XDP multi-buffer - nVidia/Mellanox: - add the support for linux bridge multicast offload - enable TC offload for egress and engress MACVLAN over bond - add support for VxLAN GBP encap/decap flows offload - extend packet offload to fully support libreswan - support tunnel mode in mlx5 IPsec packet offload - extend XDP multi-buffer support - support MACsec VLAN offload - add support for dynamic msix vectors allocation - drop RX page_cache and fully use page_pool - implement thermal zone to report NIC temperature - Netronome/Corigine: - add support for multi-zone conntrack offload - Solarflare/Xilinx: - support offloading TC VLAN push/pop actions to the MAE - support TC decap rules - support unicast PTP - Other NICs: - Broadcom (bnxt): enforce software based freq adjustments only on shared PHC NIC - RealTek (r8169): refactor to addess ASPM issues during NAPI poll - Micrel (lan8841): add support for PTP_PF_PEROUT - Cadence (macb): enable PTP unicast - Engleder (tsnep): add XDP socket zero-copy support - virtio-net: implement exact header length guest feature - veth: add page_pool support for page recycling - vxlan: add MDB data path support - gve: add XDP support for GQI-QPL format - geneve: accept every ethertype - macvlan: allow some packets to bypass broadcast queue - mana: add support for jumbo frame - Ethernet high-speed switches: - Microchip (sparx5): Add support for TC flower templates - Ethernet embedded switches: - Broadcom (b54): - configure 6318 and 63268 RGMII ports - Marvell (mv88e6xxx): - faster C45 bus scan - Microchip: - lan966x: - add support for IS1 VCAP - better TX/RX from/to CPU performances - ksz9477: add ETS Qdisc support - ksz8: enhance static MAC table operations and error handling - sama7g5: add PTP capability - NXP (ocelot): - add support for external ports - add support for preemptible traffic classes - Texas Instruments: - add CPSWxG SGMII support for J7200 and J721E - Intel WiFi (iwlwifi): - preparation for Wi-Fi 7 EHT and multi-link support - EHT (Wi-Fi 7) sniffer support - hardware timestamping support for some devices/firwmares - TX beacon protection on newer hardware - Qualcomm 802.11ax WiFi (ath11k): - MU-MIMO parameters support - ack signal support for management packets - RealTek WiFi (rtw88): - SDIO bus support - better support for some SDIO devices (e.g. MAC address from efuse) - RealTek WiFi (rtw89): - HW scan support for 8852b - better support for 6 GHz scanning - support for various newer firmware APIs - framework firmware backwards compatibility - MediaTek WiFi (mt76): - P2P support - mesh A-MSDU support - EHT (Wi-Fi 7) support - coredump support"* tag 'net-next-6.4' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next: (2078 commits) net: phy: hide the PHYLIB_LEDS knob net: phy: marvell-88x2222: remove unnecessary (void*) conversions tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp. net: amd: Fix link leak when verifying config failed net: phy: marvell: Fix inconsistent indenting in led_blink_set lan966x: Don't use xdp_frame when action is XDP_TX tsnep: Add XDP socket zero-copy TX support tsnep: Add XDP socket zero-copy RX support tsnep: Move skb receive action to separate function tsnep: Add functions for queue enable/disable tsnep: Rework TX/RX queue initialization tsnep: Replace modulo operation with mask net: phy: dp83867: Add led_brightness_set support net: phy: Fix reading LED reg property drivers: nfc: nfcsim: remove return value check of `dev_dir` net: phy: dp83867: Remove unnecessary (void*) conversions net: ethtool: coalesce: try to make user settings stick twice net: mana: Check if netdev/napi_alloc_frag returns single page net: mana: Rename mana_refill_rxoob and remove some empty lines net: veth: add page_pool stats ... List of files: /linux/drivers/net/vxlan/Makefile

abf36703d7046cd0aaf5ac5524d321851fb6bf03 - Merge branch 'vxlan-MDB-support'

Fri, 17 Mar 2023 09:05:50 +0100

Merge branch 'vxlan-MDB-support'Ido Schimmel says:====================vxlan: Add MDB supporttl;dr=====This patchset implements MDB support in the VXLAN driver, allowing it toselectively forward IP multicast traffic to VTEPs with interestedreceivers instead of flooding it to all the VTEPs as BUM. The motivatinguse case is intra and inter subnet multicast forwarding using EVPN[1][2], which means that MDB entries are only installed by the userspace control plane and no snooping is implemented, thereby avoiding alot of unnecessary complexity in the kernel.Background==========Both the bridge and VXLAN drivers have an FDB that allows them toforward Ethernet frames based on their destination MAC addresses andVLAN/VNI. These FDBs are managed using the same PF_BRIDGE/RTM_*NEIGHnetlink messages and bridge(8) utility.However, only the bridge driver has an MDB that allows it to selectivelyforward IP multicast packets to bridge ports with interested receiversbehind them, based on (S, G) and (*, G) MDB entries. When these packetsreach the VXLAN driver they are flooded using the "all-zeros" FDB entry(00:00:00:00:00:00). The entry either includes the list of all the VTEPsin the tenant domain (when ingress replication is used) or the multicastaddress of the BUM tunnel (when P2MP tunnels are used), to which all theVTEPs join.Networks that make heavy use of multicast in the overlay can benefitfrom a solution that allows them to selectively forward IP multicasttraffic only to VTEPs with interested receivers. Such a solution isdescribed in the next section.Motivation==========RFC 7432 [3] defines a "MAC/IP Advertisement route" (type 2) [4] thatallows VTEPs in the EVPN network to advertise and learn reachabilityinformation for unicast MAC addresses. Traffic destined to a unicast MACaddress can therefore be selectively forwarded to a single VTEP behindwhich the MAC is located.The same is not true for IP multicast traffic. Such traffic is simplyflooded as BUM to all VTEPs in the broadcast domain (BD) / subnet,regardless if a VTEP has interested receivers for the multicast streamor not. This is especially problematic for overlay networks that makeheavy use of multicast.The issue is addressed by RFC 9251 [1] that defines a "SelectiveMulticast Ethernet Tag Route" (type 6) [5] which allows VTEPs in theEVPN network to advertise multicast streams that they are interested in.This is done by having each VTEP suppress IGMP/MLD packets from beingtransmitted to the NVE network and instead communicate the informationover BGP to other VTEPs.The draft in [2] further extends RFC 9251 with procedures to allowefficient forwarding of IP multicast traffic not only in a given subnet,but also between different subnets in a tenant domain.The required changes in the bridge driver to support the above werealready merged in merge commit 8150f0cfb24f ("Merge branch'bridge-mcast-extensions-for-evpn'"). However, full support entails MDBsupport in the VXLAN driver so that it will be able to selectivelyforward IP multicast traffic only to VTEPs with interested receivers.The implementation of this MDB is described in the next section.Implementation==============The user interface is extended to allow user space to specify thedestination VTEP(s) and related parameters. Example usage: # bridge mdb add dev vxlan0 port vxlan0 grp 239.1.1.1 permanent dst 198.51.100.1 # bridge mdb add dev vxlan0 port vxlan0 grp 239.1.1.1 permanent dst 192.0.2.1 $ bridge -d -s mdb show dev vxlan0 port vxlan0 grp 239.1.1.1 permanent filter_mode exclude proto static dst 192.0.2.1 0.00 dev vxlan0 port vxlan0 grp 239.1.1.1 permanent filter_mode exclude proto static dst 198.51.100.1 0.00Since the MDB is fully managed by user space and since snooping is notimplemented, only permanent entries can be installed and temporaryentries are rejected by the kernel.The netlink interface is extended with a few new attributes in theRTM_NEWMDB / RTM_DELMDB request messages:[ struct nlmsghdr ][ struct br_port_msg ][ MDBA_SET_ENTRY ] struct br_mdb_entry[ MDBA_SET_ENTRY_ATTRS ] [ MDBE_ATTR_SOURCE ] struct in_addr / struct in6_addr [ MDBE_ATTR_SRC_LIST ] [ MDBE_SRC_LIST_ENTRY ] [ MDBE_SRCATTR_ADDRESS ] struct in_addr / struct in6_addr [ ...] [ MDBE_ATTR_GROUP_MODE ] u8 [ MDBE_ATTR_RTPORT ] u8 [ MDBE_ATTR_DST ] // new struct in_addr / struct in6_addr [ MDBE_ATTR_DST_PORT ] // new u16 [ MDBE_ATTR_VNI ] // new u32 [ MDBE_ATTR_IFINDEX ] // new s32 [ MDBE_ATTR_SRC_VNI ] // new u32RTM_NEWMDB / RTM_DELMDB responses and notifications are extended withcorresponding attributes.One MDB entry that can be installed in the VXLAN MDB, but not in thebridge MDB is the catchall entry (0.0.0.0 / ::). It is used to transmitunregistered multicast traffic that is not link-local and is especiallyuseful when inter-subnet multicast forwarding is required. See patch #12for a detailed explanation and motivation. It is similar to the"all-zeros" FDB entry that can be installed in the VXLAN FDB, but notthe bridge FDB."added_by_star_ex" entries--------------------------The bridge driver automatically installs (S, G) MDB port group entriesmarked as "added_by_star_ex" whenever it detects that an (S, G) entrycan prevent traffic from being forwarded via a port associated with anEXCLUDE (*, G) entry. The bridge will add the port to the port group ofthe (S, G) entry, thereby creating a new port group entry. Thecomplexity associated with these entries is not trivial, but it needs toreside in the bridge driver because it automatically installs MDBentries in response to snooped IGMP / MLD packets.The same in not true for the VXLAN MDB which is entirely managed by userspace who is fully capable of forming the correct replication lists onits own. In addition, the complexity associated with the"added_by_star_ex" entries in the VXLAN driver is higher compared to thebridge: Whenever a remote VTEP is added to the catchall entry, it needsto be added to all the existing MDB entries, as such a remote requestedall the multicast traffic to be forwarded to it. Similarly, whenever an(*, G) or (S, G) entry is added, all the remotes associated with thecatchall entry need to be added to it.Given the above, this patchset does not implement support for suchentries. One argument against this decision can be that in the futuresomeone might want to populate the VXLAN MDB in response to decapsulatedIGMP / MLD packets and not according to EVPN routes. Regardless of mydoubts regarding this possibility, it can be implemented using a newVXLAN device knob that will also enable the "added_by_star_ex"functionality.Testing=======Tested using existing VXLAN and MDB selftests under "net/" and"net/forwarding/". Added a dedicated selftest in the last patch.Patchset overview=================Patches #1-#3 are small preparations in the bridge driver. I plan tosubmit them separately together with an MDB dump test case.Patches #4-#6 are additional preparations centered around the extractionof the MDB netlink handlers from the bridge driver to the commonrtnetlink code. This allows reusing the existing MDB netlink messagesfor the configuration of the VXLAN MDB.Patches #7-#9 include more small preparations in the common rtnetlinkcode and the VXLAN driver.Patch #10 implements the MDB control path in the VXLAN driver, whichwill allow user space to create, delete, replace and dump MDB entries.Patches #11-#12 implement the MDB data path in the VXLAN driver,allowing it to selectively forward IP multicast traffic according to thematched MDB entry.Patch #13 finally enables MDB support in the VXLAN driver.iproute2 patches can be found here [6].Note that in order to fully support the specifications in [1] and [2],additional functionality is required from the data path. However, it canbe achieved using existing kernel interfaces which is why it is notdescribed here.Changelog=========Since v1 [7]:Patch #9: Use htons() in 'case' instead of ntohs() in 'switch'.Since RFC [8]:Patch #3: Use NL_ASSERT_DUMP_CTX_FITS().Patch #3: memset the entire context when moving to the next device.Patch #3: Reset sequence counters when moving to the next device.Patch #3: Use NL_SET_ERR_MSG_ATTR() in rtnl_validate_mdb_entry().Patch #7: Remove restrictions regarding mixing of multicast and unicastremote destination IPs in an MDB entry. While such configuration doesnot make sense to me, it is no forbidden by the VXLAN FDB code and doesnot crash the kernel.Patch #7: Fix check regarding all-zeros MDB entry and source.Patch #11: New patch.[1] https://datatracker.ietf.org/doc/html/rfc9251[2] https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-irb-mcast[3] https://datatracker.ietf.org/doc/html/rfc7432[4] https://datatracker.ietf.org/doc/html/rfc7432#section-7.2[5] https://datatracker.ietf.org/doc/html/rfc9251#section-9.1[6] https://github.com/idosch/iproute2/commits/submit/mdb_vxlan_rfc_v1[7] https://lore.kernel.org/netdev/20230313145349.3557231-1-idosch@nvidia.com/[8] https://lore.kernel.org/netdev/20230204170801.3897900-1-idosch@nvidia.com/====================Signed-off-by: David S. Miller List of files: /linux/drivers/net/vxlan/Makefile

a3a48de5eade770e911d35291217bdd69ce04ef1 - vxlan: mdb: Add MDB control path support

Wed, 15 Mar 2023 14:11:51 +0100

vxlan: mdb: Add MDB control path supportImplement MDB control path support, enabling the creation, deletion,replacement and dumping of MDB entries in a similar fashion to thebridge driver. Unlike the bridge driver, each entry stores a list ofremote VTEPs to which matched packets need to be replicated to and not alist of bridge ports.The motivating use case is the installation of MDB entries by a userspace control plane in response to received EVPN routes. As such, onlyallow permanent MDB entries to be installed and do not implementsnooping functionality, avoiding a lot of unnecessary complexity.Since entries can only be modified by user space under RTNL, use RTNL asthe write lock. Use RCU to ensure that MDB entries and remotes are notfreed while being accessed from the data path during transmission.In terms of uAPI, reuse the existing MDB netlink interface, but add afew new attributes to request and response messages:* IP address of the destination VXLAN tunnel endpoint where the multicast receivers reside.* UDP destination port number to use to connect to the remote VXLAN tunnel endpoint.* VXLAN VNI Network Identifier to use to connect to the remote VXLAN tunnel endpoint. Required when Ingress Replication (IR) is used and the remote VTEP is not a member of originating broadcast domain (VLAN/VNI) [1].* Source VNI Network Identifier the MDB entry belongs to. Used only when the VXLAN device is in external mode.* Interface index of the outgoing interface to reach the remote VXLAN tunnel endpoint. This is required when the underlay destination IP is multicast (P2MP), as the multicast routing tables are not consulted.All the new attributes are added under the 'MDBA_SET_ENTRY_ATTRS' nestwhich is strictly validated by the bridge driver, thereby automaticallyrejecting the new attributes.[1] https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-irb-mcast#section-3.2.2Signed-off-by: Ido Schimmel Reviewed-by: Nikolay Aleksandrov Signed-off-by: David S. Miller List of files: /linux/drivers/net/vxlan/Makefile

4f2c0a4acffbec01079c28f839422e64ddeff004 - Merge branch 'main' into zstd-linus

Wed, 14 Dec 2022 01:21:55 +0100

Merge branch 'main' into zstd-linus List of files: /linux/drivers/net/vxlan/Makefile

14e77332e74603efab8347c89d3cda447c3b97c9 - Merge branch 'main' into zstd-next

Sat, 22 Oct 2022 01:00:35 +0200

Merge branch 'main' into zstd-next List of files: /linux/drivers/net/vxlan/Makefile

8bb5e7f4dcd9b9ef22a3ea25c9066a8a968f12dd - Merge branch 'next' into for-linus

Tue, 02 Aug 2022 19:06:12 +0200

Merge branch 'next' into for-linusPrepare input updates for 5.20 (or 6.0) merge window. List of files: /linux/drivers/net/vxlan/Makefile

03ab8e6297acd1bc0eedaa050e2a1635c576fd11 - Merge tag 'v5.18'

Tue, 31 May 2022 15:13:23 +0200

Merge tag 'v5.18'Linux 5.18 List of files: /linux/drivers/net/vxlan/Makefile

690e179059e7e89040d1cd564e39761567a8d5dc - Merge tag 'v5.18' into next

Sat, 28 May 2022 01:40:01 +0200

Merge tag 'v5.18' into nextSync up with mainline to get updates to OMAP4 keypad driver and otherupstream goodies. List of files: /linux/drivers/net/vxlan/Makefile

0aea30a07ec6b50de0fc5f5b2ec34a68ead86b61 - Merge tag 'asoc-fix-v5.18-rc3' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus

Tue, 19 Apr 2022 17:26:01 +0200

Merge tag 'asoc-fix-v5.18-rc3' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linusASoC: Fixes for v5.18A collection of fixes that came in since the merge window, plus one newdevice ID for an x86 laptop. Nothing that really stands out withparticularly big impact outside of the affected device. List of files: /linux/drivers/net/vxlan/Makefile

651a88798412e216f337d70181127e847f00a4b7 - Merge branch 'topic/cs35l41' into for-next

Wed, 13 Apr 2022 10:43:03 +0200

Merge branch 'topic/cs35l41' into for-nextPull CS35L41 codec updatesSigned-off-by: Takashi Iwai List of files: /linux/drivers/net/vxlan/Makefile

c16c8bfa09d5f318c1bd65698d058d3739970c24 - Merge drm/drm-next into drm-intel-gt-next

Tue, 12 Apr 2022 10:28:42 +0200

Merge drm/drm-next into drm-intel-gt-nextPull in TTM changes needed for DG2 CCS enabling from Ram.Signed-off-by: Joonas Lahtinen List of files: /linux/drivers/net/vxlan/Makefile

83970cd63b9f864525761137b500113ab0b49c94 - Merge drm/drm-next into drm-intel-next

Mon, 11 Apr 2022 15:01:56 +0200

Merge drm/drm-next into drm-intel-nextSync up with v5.18-rc1, in particular to get 5e3094cfd9fb("drm/i915/xehpsdv: Add has_flat_ccs to device info").Signed-off-by: Jani Nikula List of files: /linux/drivers/net/vxlan/Makefile