From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus <torvalds@linux-foundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: linux-next: build failure of Linus' tree
Date: Thu, 24 Nov 2011 11:21:17 +1100 [thread overview]
Message-ID: <20111124112117.f9abeb7a3f4868be71389372@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
Hi all,
today's linux-next build of Linus' (x86_64_allmodconfig) failed like this:
drivers/staging/iio/industrialio-core.c: In function 'iio_event_getfd':
drivers/staging/iio/industrialio-core.c:262:32: error: 'ev_int' undeclared (first use in this function)
Caused by commit b46413367961 ("iio: fix a leak due to improper use of
anon_inode_getfd()").
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-11-24 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 0:21 Stephen Rothwell [this message]
2011-11-24 8:09 ` linux-next: build failure of Linus' tree Sasha Levin
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=20111124112117.f9abeb7a3f4868be71389372@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).