From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-media@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL for v4.20-rc1] new experimental media request API
Date: Wed, 31 Oct 2018 23:37:02 -0300 [thread overview]
Message-ID: <20181031233702.13a501ea@coco.lan> (raw)
In-Reply-To: <CAHk-=wi5wkZtwZQfjVudLtS-Ej9pvaqu6=xM1msoBF8sMuTc_A@mail.gmail.com>
Em Wed, 31 Oct 2018 15:32:03 -0700
Linus Torvalds <torvalds@linux-foundation.org> escreveu:
> On Wed, Oct 31, 2018 at 11:05 AM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > But pulled,
>
> I have no idea how I missed this during the actual test compile after
> the pull (and yes, I'm sure I did one), but after doing a couple of
> more pulls I finally did notice.
>
> After the media pull I get this warning:
>
> ./usr/include/linux/v4l2-controls.h:1105: found __[us]{8,16,32,64}
> type without #include <linux/types.h>
>
> and sure enough, the recent changes to
>
> include/uapi/linux/v4l2-controls.h
>
> add those new structures use the "__uXY" types without including the
> header to define them.
>
> It's harmless in the short term and the kernel build itself obviously
> doesn't care apart from the warning, but please fix it.
I also missed this one. Perhaps it depends on gcc version, or is it
a new warning after some changes? I remember there was some patchsets
floating around related to change some warnings.
Anyway, I'll send you a fix for it soon.
Thanks,
Mauro
prev parent reply other threads:[~2018-11-01 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 13:53 [GIT PULL for v4.20-rc1] new experimental media request API Mauro Carvalho Chehab
2018-10-31 18:05 ` Linus Torvalds
2018-10-31 18:40 ` Mauro Carvalho Chehab
2018-11-11 20:28 ` Pavel Machek
2018-11-12 8:58 ` Hans Verkuil
2018-10-31 22:32 ` Linus Torvalds
2018-11-01 2:37 ` Mauro Carvalho Chehab [this message]
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=20181031233702.13a501ea@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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).