public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Mar 17
Date: Wed, 17 Mar 2021 13:00:45 +0100	[thread overview]
Message-ID: <YFHvbXwwRn5scIcz@osiris> (raw)
In-Reply-To: <20210317194241.1bf057bd@canb.auug.org.au>

On Wed, Mar 17, 2021 at 07:42:41PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> News: there will be no linux-next release on Friday this week.
> 
> Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> so please be careful if you are trying to bisect a bug.
> 
> News: if your -next included tree is based on Linus' tree tag
> v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
> consider rebasing it onto v5.12-rc2. Also, please check any branches
> merged into your branch.
> 
> Changes since 20210316:
> 
> New tree: cifsd
> 
> The cifsd tree gained a build failure for which I applied a patch.
> 
> The drm-intel tree gained a conflict against the drm tree.
> 
> The tip tree gained a build failure so I used the version from
> next-20210316.
> 
> The rcu tree gained a build failure so I used the version from
> next-20210316.
> 
> Non-merge commits (relative to Linus' tree): 4404
>  4125 files changed, 288074 insertions(+), 79674 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

This does unfortunately not compile on s390 due to commit 72dd1ce7ebd3
("quota: wire up quotactl_path").

The patch below fixes it:

diff --git a/arch/s390/kernel/syscalls/syscall.tbl b/arch/s390/kernel/syscalls/syscall.tbl
index 4aeaa89fa774..a421905c36e8 100644
--- a/arch/s390/kernel/syscalls/syscall.tbl
+++ b/arch/s390/kernel/syscalls/syscall.tbl
@@ -445,4 +445,4 @@
 440  common	process_madvise		sys_process_madvise		sys_process_madvise
 441  common	epoll_pwait2		sys_epoll_pwait2		compat_sys_epoll_pwait2
 442  common	mount_setattr		sys_mount_setattr		sys_mount_setattr
-443  common	quotactl_path		sys_quotactl_path
+443  common	quotactl_path		sys_quotactl_path		sys_quotactl_path

  reply	other threads:[~2021-03-17 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  8:42 linux-next: Tree for Mar 17 Stephen Rothwell
2021-03-17 12:00 ` Heiko Carstens [this message]
2021-03-17 14:53   ` Jan Kara
  -- strict thread matches above, loose matches on Subject: below --
2026-03-17 17:03 Mark Brown
2025-03-17 12:59 Stephen Rothwell
2023-03-17  2:36 Stephen Rothwell
2022-03-17  8:58 Stephen Rothwell
2020-03-17  9:37 Stephen Rothwell
2016-03-17  5:19 Stephen Rothwell
2015-03-17  6:35 Stephen Rothwell
2014-03-17 10:53 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YFHvbXwwRn5scIcz@osiris \
    --to=hca@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox