archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <>
To: Stephen Rothwell <>
Cc: Matthew Wilcox <>,
Subject: Re: linux-next: m68k/semaphore build failure
Date: Tue, 27 May 2008 18:10:51 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0805271809520.4081@anakin> (raw)
In-Reply-To: <>

On Tue, 27 May 2008, Stephen Rothwell wrote:
> Today's linux-next build (m68k multi_defconfig) failed like this:
> drivers/input/keyboard/hil_kbd.c:336: error: 'PCI_VENDOR_ID_HP' undeclared (first use in this function)
> drivers/input/keyboard/hil_kbd.c:336: error: (Each undeclared identifier is reported only once
> drivers/input/keyboard/hil_kbd.c:336: error: for each function it appears in.)
> This is caused by commit fd7c1a9773fd107674216b63a752f21ba6495045 ("Add
> missing semaphore.h includes") from the semaphore tree.  That commit adds
> a linux/semaphore.h include but removes the linux/pci_ids.h include.


I'd swear I reported this to Willy the first time it appeared, but according
to my mail logs, I never did...



Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2008-05-27 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 10:10 linux-next: m68k/semaphore build failure Stephen Rothwell
2008-05-27 16:10 ` Geert Uytterhoeven [this message]
2008-05-28  6:04   ` Stephen Rothwell
2008-05-31 17:20     ` Matthew Wilcox
2008-06-01  2:18       ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0805271809520.4081@anakin \ \ \ \ \

* 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).