linux-next: Tree for Mar 18

linux-next: Tree for Mar 18

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]

Hi all,

Changes since 20260317:

The mm-unstable tree gained a build failure, I used the version from
next-20260318 instead.

The bluetooth tree acquired a conflict with the net tree.

The drm tree acquired a conflict with the drm-misc-fixes tree.

The sound-asoc lost it's build failure.

Non-merge commits (relative to Linus' tree): 6514
 6652 files changed, 440309 insertions(+), 133980 deletions(-)

----------------------------------------------------------------------------

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There is also the merge.log file in the Next
directory.  Between each merge, the tree was built with a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
and a native build of tools/perf.  After the final fixups (if any), I do
an x86_64 modules_install followed by builds for x86_64 allnoconfig,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.

Below is a summary of the state of the merge.

I am currently merging 412 trees (counting Linus' and 123 trees of bug
fix patches pending for the current release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Thanks to Paul Gortmaker for triage and bug fixes.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: Tree for Mar 18 (landlock docs)

[Randy Dunlap]

On 3/18/26 9:52 AM, Mark Brown wrote:
> Hi all,
> 
> Changes since 20260317:
> 

linux-next/Documentation/userspace-api/landlock.rst:198: ERROR: Error in "code-block" directive:
maximum 1 argument(s) allowed, 105 supplied.
^^^^^^^^^^^^^^^^^^^^^^^^^^

.. code-block:: c
    __u32 restrict_flags =


Please insert a blank line between ".. code-block:: c"
and the code.


d37d3347aa59 ("landlock: Expand restrict flags example for ABI version 8")

-- 
~Randy

Re: linux-next: Tree for Mar 18 (landlock docs)

[Mickaël Salaün]

On Wed, Mar 18, 2026 at 03:12:39PM -0700, Randy Dunlap wrote:
> 
> 
> On 3/18/26 9:52 AM, Mark Brown wrote:
> > Hi all,
> > 
> > Changes since 20260317:
> > 
> 
> linux-next/Documentation/userspace-api/landlock.rst:198: ERROR: Error in "code-block" directive:
> maximum 1 argument(s) allowed, 105 supplied.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> .. code-block:: c
>     __u32 restrict_flags =
> 
> 
> Please insert a blank line between ".. code-block:: c"
> and the code.
> 

Thanks, it's now fixed and rebased.

> 
> d37d3347aa59 ("landlock: Expand restrict flags example for ABI version 8")
> 
> -- 
> ~Randy
> 
>