The Linux 7.4 merge window has opened, and according to Phoronix's review of the incoming changes, the kernel is "hopefully going to be this year's Long Term Support (LTS) kernel version" — a designation that matters far more to infrastructure planners than any individual feature in the release.
LTS kernels are the versions that Linux distributions, cloud providers and hardware appliance vendors build their long-lived product lines on. A kernel selected for LTS typically receives security and maintenance updates for years after its initial release, which means the 7.4 decision, once formally made, will quietly shape server upgrade roadmaps for a long time. For organisations planning fleet standardisation, the practical question is not which shiny device gets support on day one — it is which kernel their chosen distribution will standardise on for the next several years.
Two caveats are worth stating plainly. First, the merge window is where maintainers propose and integrate changes; the contents can still shift, be reverted or be reworked before the final release ships. Second, LTS status is formally decided at release time, not during the merge window. Phoronix's phrasing — "hopefully" LTS — signals a strong expectation from the community rather than a committed guarantee. Enterprises should treat 7.4's LTS candidacy as a planning assumption to watch, not a fact to build a contract around yet.
Hardware enablement, by maturity
Beyond the LTS question, 7.4 carries a set of hardware-enablement items that sit at noticeably different stages of readiness.
The most iterative is AMD's ongoing Zen 6 support. This is incremental work in the standard mould of upstream CPU enablement — the kind of change that lands early and matures across release cycles. For server operators, the relevance is concrete: Zen 6 support maturing in mainline Linux is a precondition for distributions and hypervisor stacks to fully back AMD's newer server silicon, which feeds directly into hardware roadmaps for both on-premises and cloud-hosted fleets.
At the opposite end of the maturity spectrum is Apple's platform work. Phoronix reports initial bring-up for the Apple M4 and A18 Pro in 7.4. The key word is initial. Early-stage enablement is best read as context about the direction of upstream Apple Silicon support — interesting for developers and workstation users watching the ecosystem, but not a procurement trigger. Nobody should be specifying hardware on the strength of first-pass support.
Between those sits Valve's Steam Frame VR headset support: a niche consumer device in a niche category, but a worthwhile signal that another piece of hardware is being wired up in the mainline kernel rather than carried as an out-of-tree patch. For the open-source community, upstream visibility for consumer hardware remains a small but meaningful health indicator.
The takeaway for planners
The sequence for anyone making kernel-dependent decisions is straightforward: watch the 7.4 release, confirm whether the LTS designation is formally granted, then — the step that actually determines production outcomes — watch which distributions adopt 7.4 as their long-term base. That adoption pattern, not any individual hardware line item, is what decides when organisations can realistically move.
Feature lists generate headlines; LTS designations generate roadmaps. For infrastructure teams, the densest part of the 7.4 story is the smallest sentence in it: whether this becomes the LTS kernel everything else is built on.
Linux 7.4 的 merge window 已經開啟，根據 Phoronix 對即將納入的變更所作的梳理，該 kernel「有望成為今年的長期支援（Long Term Support，LTS）kernel 版本」——這項指定對基建規劃人員的重要性，遠超乎版本中任何個別功能。
LTS kernel 正是 Linux 發行版、雲端服務供應商及硬件設備廠商用以建立其長壽產品線的版本。獲選為 LTS 的 kernel 通常在首次發布後仍會多年獲得安全及維護更新，這意味著 7.4 的決定一旦正式落實，將會在往後一段長時間內默默塑造伺服器升級路線圖。對於計劃統一機隊標準的機構而言，實際問題並非哪項亮眼設備能在發布首日獲支援，而是它們所選發行版未來數年將以哪個 kernel 為標準。
有兩點須明確說明。第一，merge window 是維護者提出及整合變更的階段；內容在最終版本發布前仍可能變動、回退或重新修訂。第二，LTS 資格是在發布時正式決定，而非在 merge window 期間。Phoronix 的措辭——「有望」成為 LTS——反映的是社群的強烈預期，而非已作承諾的保證。企業應將 7.4 的 LTS 候選資格視為需要持續觀察的規劃假設，而非現時據以訂立合約的事實。
硬件支援，按成熟度劃分
除了 LTS 問題之外，7.4 還包含一系列硬件支援項目，它們的就緒程度明顯處於不同階段。
最具持續迭代性的是 AMD 對 Zen 6 的支援工作。這是上游 CPU 支援中常見的漸進式工程——此類變更往往較早納入，並在多個發布週期中逐步成熟。對伺服器系統維護人員而言，關聯相當直接：Zen 6 支援在主線 Linux 中成熟，是各發行版及 hypervisor 技術堆疊全面支援 AMD 較新伺服器晶片的先決條件，這直接影響本地及雲端機隊的硬件路線圖。
在成熟度光譜的另一端，是 Apple 的平台工作。Phoronix 報導 7.4 中已為 Apple M4 及 A18 Pro 進行初步 bring-up。關鍵詞是初步。早期階段的硬件支援，宜解讀為上游 Apple Silicon 支援方向的參考背景——對關注此生態系統的開發者及工作站用戶而言饒有興趣，但不構成採購依據。不應有人憑首輪支援就敲定硬件規格。
夾在兩者之間的是 Valve Steam Frame VR 頭戴設備的支援：屬小眾類別中的小眾消費產品，但這是一個值得注意的信號——又一件硬件正接入主線 kernel，而非以外置（out-of-tree）補丁形式維護。對開源社群而言，消費級硬件進入上游始終是一項雖小卻有意義的健康指標。
給規劃人員的要點
對任何需要就 kernel 作決定的人來說，流程相當直接：留意 7.4 的發布，確認 LTS 指定是否正式獲得——然後，才是真正決定生產環境結果的一步——留意哪些發行版採用 7.4 作為長期基礎。決定機構何時可以實際遷移的，是這種採用模式，而非任何個別硬件項目。
功能清單會成為頭條新聞；LTS 指定則會生成路線圖。對基建團隊而言，7.4 報道中最關鍵的部分，正是其中最簡短的一句：它是否會成為一切其他事物所依託的 LTS kernel。