All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
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 Jul 10
Date: Mon, 13 Jul 2020 08:01:52 +1000	[thread overview]
Message-ID: <20200713080152.63ee1246@canb.auug.org.au> (raw)
In-Reply-To: <20200712155604.GA342822@smile.fi.intel.com>

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

Hi Andy,

On Sun, 12 Jul 2020 18:56:04 +0300 Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>
> On Fri, Jul 10, 2020 at 06:33:18PM +1000, Stephen Rothwell wrote:
> > 
> > Changes since 20200709:
> 
> I can't build it on Debian with Sparse enabled
> 
> CC      init/main.o
> init/main.c:760:20: warning: no previous prototype for ‘mem_encrypt_init’ [-Wmissing-prototypes]
> 760 | void __init __weak mem_encrypt_init(void) { }
> |                    ^~~~~~~~~~~~~~~~
> CHECK   /home/andy/prj/linux-topic-uart/init/main.c
> include/linux/compiler.h:309:16: error: typename in expression
> include/linux/compiler.h:309:16: error: Expected ) in function call
> include/linux/compiler.h:309:16: error: got :
> ...
> (All READ_ONCE() entries fail)
> 
> Is it known issue?

Not that I am aware of at the moment.  Does next-20200709 work?  Does
Linus' tree work?  The only obvious thing I can think of is commit

6ec4476ac825 ("Raise gcc version requirement to 4.9")

The commmit message says:

    Using _Generic also means that you will need to have a very recent
    version of 'sparse', but thats easy to build yourself, and much less of
    a hassle than some old gcc version can be.

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2020-07-12 22:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  8:33 linux-next: Tree for Jul 10 Stephen Rothwell
2020-07-10 18:02 ` linux-next: Tree for Jul 10 (drivers/net/phy/mdio-thunder & mdio-mvusb) Randy Dunlap
2020-07-12 15:56 ` linux-next: Tree for Jul 10 Andy Shevchenko
2020-07-12 22:01   ` Stephen Rothwell [this message]
2020-07-13  2:19     ` Randy Dunlap
2020-07-13  2:26       ` Randy Dunlap
2020-07-13  2:27       ` Linus Torvalds
2020-07-13  2:33         ` Randy Dunlap
2020-07-13 11:01           ` Andy Shevchenko
  -- strict thread matches above, loose matches on Subject: below --
2023-07-10  1:38 Stephen Rothwell
2019-07-10 11:10 Stephen Rothwell
2018-07-10  7:45 Stephen Rothwell
2017-07-10  5:58 Stephen Rothwell
2015-07-10  5:48 Stephen Rothwell
2014-07-10  7:20 Stephen Rothwell
2013-07-10  5:51 Stephen Rothwell
2013-07-10  5:51 ` 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=20200713080152.63ee1246@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andriy.shevchenko@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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.