From: Vinson Lee <vlee@freedesktop.org>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: trinity@vger.kernel.org
Subject: Re: [PATCH v2] Remove unused variable in fds/drm.c.
Date: Fri, 4 Dec 2015 10:49:42 -0800 [thread overview]
Message-ID: <CACKvgLHsZMP-XpMEo-FVWiES4d4nw4YBgoybsf7jXEdgUHbUOQ@mail.gmail.com> (raw)
In-Reply-To: <20151204180701.GA28404@codemonkey.org.uk>
On Fri, Dec 4, 2015 at 10:07 AM, Dave Jones <davej@codemonkey.org.uk> wrote:
> On Fri, Dec 04, 2015 at 02:18:52AM -0800, Vinson Lee wrote:
> > Fix build error with GCC 5.2.1.
> >
> > CC fds/drm.o
> > fds/drm.c: In function ‘open_drm_fds’:
> > fds/drm.c:70:15: error: unused variable ‘i’ [-Werror=unused-variable]
> > unsigned int i;
> > ^
>
> Applied. I wonder why debian's 5.2.1 didn't pick up on this.
> Judging by your other patches, I'm guessing this is Fedora's version ?
>
> Dave
>
Yes, the error was from GCC on Fedora.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/5.2.1/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap
--enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared
--enable-threads=posix --enable-checking=release --enable-multilib
--with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-gnu-unique-object
--enable-linker-build-id --with-linker-hash-style=gnu --enable-plugin
--enable-initfini-array --disable-libgcj --with-isl --enable-libmpx
--enable-gnu-indirect-function --with-tune=generic --with-arch_32=i686
--build=x86_64-redhat-linux
Thread model: posix
gcc version 5.2.1 20151104 (Red Hat 5.2.1-5) (GCC)
Vinson
prev parent reply other threads:[~2015-12-04 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 10:18 [PATCH v2] Remove unused variable in fds/drm.c Vinson Lee
2015-12-04 18:07 ` Dave Jones
2015-12-04 18:49 ` Vinson Lee [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=CACKvgLHsZMP-XpMEo-FVWiES4d4nw4YBgoybsf7jXEdgUHbUOQ@mail.gmail.com \
--to=vlee@freedesktop.org \
--cc=davej@codemonkey.org.uk \
--cc=trinity@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).