From: Sasha Levin <levinsasha928@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: build failure of Linus' tree
Date: Thu, 24 Nov 2011 10:09:05 +0200 [thread overview]
Message-ID: <1322122145.4248.2.camel@lappy> (raw)
In-Reply-To: <20111124112117.f9abeb7a3f4868be71389372@canb.auug.org.au>
On Thu, 2011-11-24 at 11:21 +1100, Stephen Rothwell wrote:
> 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.
I've sent a patch yesterday named "iio: Fix build error in
industrialio-core.c" which should fix that.
--
Sasha.
prev parent reply other threads:[~2011-11-24 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 0:21 linux-next: build failure of Linus' tree Stephen Rothwell
2011-11-24 8:09 ` Sasha Levin [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=1322122145.4248.2.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 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.