All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Subject: Re: linux-next: build warning in Linus' tree tree
Date: Fri, 2 Nov 2018 07:30:16 -0300	[thread overview]
Message-ID: <20181102073005.4fb45747@coco.lan> (raw)
In-Reply-To: <20181101082820.76abf19e@canb.auug.org.au>

Hi Stephen,

Em Thu, 1 Nov 2018 08:28:20 +1100
Stephen Rothwell <sfr@canb.auug.org.au> escreveu:

> Hi all,
> 
> Building Linus' tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
> 
> ./usr/include/linux/v4l2-controls.h:1105: found __[us]{8,16,32,64} type without #include <linux/types.h>
> 
> Introduced by commit
> 
>   c27bb30e7b6d ("media: v4l: Add definitions for MPEG-2 slice format and metadata")
> 

How are you building it? Here this warning doesn't pop up.

I'm using here:

	gcc (GCC) 8.2.1 20181011 (Red Hat 8.2.1-4)

And I'm using:

$ make ARCH=x86_64  CF=-D__CHECK_ENDIAN__ CONFIG_DEBUG_SECTION_MISMATCH=y W=1 CHECK='' M=drivers/media

(it is not a full build, but it should be enough to get warnings at the
media subsystem)

Thanks,
Mauro

  parent reply	other threads:[~2018-11-02 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 21:28 linux-next: build warning in Linus' tree tree Stephen Rothwell
2018-11-01  2:38 ` Mauro Carvalho Chehab
2018-11-02 10:30 ` Mauro Carvalho Chehab [this message]
2018-11-02 10:34   ` Mauro Carvalho Chehab

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=20181102073005.4fb45747@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul.kocialkowski@bootlin.com \
    --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 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.