From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
dmitry.torokhov@gmail.com
Subject: Re: linux-next: Tree for May 29
Date: Thu, 29 May 2008 09:44:54 -0700 [thread overview]
Message-ID: <20080529094454.3605aa5c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080529182556.2994310a.sfr@canb.auug.org.au>
On Thu, 29 May 2008 18:25:56 +1000 Stephen Rothwell wrote:
> Merging input/next
Most randconfig builds end with i8042 build errors (on i386 or x86_64)
when CONFIG_PNP=n:
linux-next-20080529/drivers/input/serio/i8042-x86ia64io.h:590: error: 'i8042_nopnp' undeclared (first use in this function)
linux-next-20080529/drivers/input/serio/i8042-x86ia64io.h:590: error: (Each undeclared identifier is reported only once
linux-next-20080529/drivers/input/serio/i8042-x86ia64io.h:590: error: for each function it appears in.)
make[3]: *** [drivers/input/serio/i8042.o] Error 1
---
~Randy
"He closes his eyes and drops the goggles. You can't get hurt
by looking at a bitmap. Or can you?"
next prev parent reply other threads:[~2008-05-29 16:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 8:25 linux-next: Tree for May 29 Stephen Rothwell
2008-05-29 16:44 ` Randy Dunlap [this message]
2008-05-29 16:56 ` [PATCH linux-next] serio: add ifdef for i8042 build fix Randy Dunlap
2008-05-29 18:46 ` Dmitry Torokhov
2008-05-29 19:17 ` Randy Dunlap
2008-06-02 8:44 ` Jiri Kosina
2008-05-29 18:28 ` [PATCH] linux-next: Tree for May 29 - build failure s390x -typo in ccw_timeout_log() Kamalesh Babulal
2008-05-29 19:06 ` Greg KH
2008-05-29 20:21 ` [BUG] linux-next: Tree for May 29 - WARNING: at kernel/lockdep.c:2680 Kamalesh Babulal
2009-05-29 4:50 linux-next: Tree for May 29 Stephen Rothwell
2012-05-29 5:18 Stephen Rothwell
2013-05-29 5:41 Stephen Rothwell
2014-05-29 9:57 Stephen Rothwell
2015-05-29 12:18 Stephen Rothwell
2017-05-29 3:55 Stephen Rothwell
2018-05-29 10:44 Stephen Rothwell
2019-05-29 5:18 Stephen Rothwell
2020-05-29 11:56 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=20080529094454.3605aa5c.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).