All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Juergen Gross <jgross@suse.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Xen Devel <xen-devel@lists.xenproject.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the xen-tip tree
Date: Wed, 15 Sep 2021 11:11:48 +1000	[thread overview]
Message-ID: <20210915111148.54ddb83d@canb.auug.org.au> (raw)

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

Hi all,

After merging the xen-tip tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/base/power/trace.c: In function 'generate_pm_trace':
drivers/base/power/trace.c:170:10: error: 'return' with a value, in function returning void [-Werror=return-type]
  170 |   return 0;
      |          ^
drivers/base/power/trace.c:163:6: note: declared here
  163 | void generate_pm_trace(const void *tracedata, unsigned int user)
      |      ^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors

Caused by commit

  38b6c7137e13 ("PM: base: power: don't try to use non-existing RTC for storing data")

I used the xen-tip tree from next-20210914 for today.
-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2021-09-15  1:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15  1:11 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-30  5:12 linux-next: build failure after merge of the xen-tip tree Stephen Rothwell
2018-07-30  7:40 ` Oleksandr Andrushchenko
2018-08-16  0:09 ` Stephen Rothwell
2017-08-31  5:22 Stephen Rothwell
2015-04-13  8:09 Stephen Rothwell
2015-04-13  8:36 ` Bob Liu
2015-04-15  5:00   ` Stephen Rothwell
2015-04-15 10:03   ` David Vrabel
2015-04-15 10:03     ` David Vrabel

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=20210915111148.54ddb83d@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.