From: Eric Paris <eparis@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Richard Guy Briggs <rgb@redhat.com>
Subject: Re: linux-next: build warning after merge of the final tree (in Linus' tree)
Date: Fri, 17 May 2013 15:08:59 -0400 [thread overview]
Message-ID: <1368817739.1372.5.camel@localhost> (raw)
In-Reply-To: <CAOh2x=nNNdgndfXCAQ7-oXDcuiNwAbNSb3_DgYuGsO8cPC__5g@mail.gmail.com>
On Fri, 2013-05-17 at 10:47 +0530, Viresh Kumar wrote:
> On Wed, May 15, 2013 at 7:02 PM, Eric Paris <eparis@redhat.com> wrote:
> > On Wed, 2013-05-15 at 13:20 +1000, Stephen Rothwell wrote:
> >> Hi ,
> >>
> >> After merging the final tree, today's linux-next build (i386 defconfig)
> >> produced this warning:
> >>
> >> kernel/auditfilter.c: In function 'audit_data_to_entry':
> >> kernel/auditfilter.c:426:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
> >>
> >> Introduced by commit 780a7654cee8 ("audit: Make testing for a valid
> >> loginuid explicit") from Linus' tree.
> >
> > Thank you, I'll fix it up. What am I likely missing that I don't see it
> > on my builds? I'm using gcc 4.8. Is there a config option that enables
> > additional warnings?
>
> Is this fixed? I couldn't find a relevant patch in linux-next/master for it.
Something should be posted by the end of the day. Sorry for the delay.
next prev parent reply other threads:[~2013-05-17 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 3:20 linux-next: build warning after merge of the final tree (in Linus' tree) Stephen Rothwell
2013-05-15 13:32 ` Eric Paris
2013-05-15 22:25 ` Stephen Rothwell
2013-05-17 5:17 ` Viresh Kumar
2013-05-17 19:08 ` Eric Paris [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-10 6:36 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=1368817739.1372.5.camel@localhost \
--to=eparis@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rgb@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=viresh.kumar@linaro.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.