linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the header_cleanup tree
Date: Mon, 18 Dec 2023 23:59:40 -0500	[thread overview]
Message-ID: <20231219045940.tl42emmfdcyzjruz@moria.home.lan> (raw)
In-Reply-To: <20231219152545.54ac44cd@canb.auug.org.au>

On Tue, Dec 19, 2023 at 03:25:45PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the header_cleanup tree, today's linux-next build (s390
> defconfig) failed like this:
> 
> arch/s390/kernel/signal.c: In function 'arch_do_signal_or_restart':
> arch/s390/kernel/signal.c:491:17: error: implicit declaration of function 'rseq_signal_deliver' [-Werror=implicit-function-declaration]
>   491 |                 rseq_signal_deliver(&ksig, regs);
>       |                 ^~~~~~~~~~~~~~~~~~~
> 
> Presumably caused by commit
> 
>   cd1146fc0ad3 ("rseq: Split out rseq.h from sched.h")
> 
> I have applied the following patch for today:

I've applied the same fixup to my tree.

  reply	other threads:[~2023-12-19  4:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  4:25 linux-next: build failure after merge of the header_cleanup tree Stephen Rothwell
2023-12-19  4:59 ` Kent Overstreet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18  6:40 Stephen Rothwell
2023-12-19  3:57 ` Stephen Rothwell
2023-12-19 13:53   ` Ville Syrjälä
2023-12-18  6:29 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=20231219045940.tl42emmfdcyzjruz@moria.home.lan \
    --to=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).