mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andre Haupt <andre@finow14.de>, torvalds@osdl.org
Cc: marcel@holtmann.org, linux-kernel@vger.kernel.org
Subject: Re: hci_sock.c build failure
Date: Wed, 12 Sep 2007 05:07:26 -0700	[thread overview]
Message-ID: <20070912120726.GA13170@kroah.com> (raw)
In-Reply-To: <20070912120407.GB13003@kroah.com>

On Wed, Sep 12, 2007 at 05:04:07AM -0700, Greg KH wrote:
> On Wed, Sep 12, 2007 at 05:02:53AM -0700, Greg KH wrote:
> > On Wed, Sep 12, 2007 at 11:29:29AM +0200, Andre Haupt wrote:
> > > Hi,
> > > 
> > > I did a make randconfig and then make C=1.
> > > 
> > > hci_sock.c fails to build because it doesnt know compat_timeval (i
> > > guess).
> > > 
> > > find the error message and the config attached.
> > 
> > It's not even a randconfig issue, my build dies too (this is Linus's
> > current tree.)
> > 
> > Time to poke through the 10 bluetooth patches that were just added...
> 
> It was 767c5eb5d35aeb85987143f0a730bc21d3ecfb3d that caused it.  It
> needs a .h file added to the file, patch forthcoming...

No, this is worse, i386 doesn't have a compat_timeval structure defined,
nor does any other 32 bit platform.

Marcel, I think you need to use a different structure, care to fix this
up?

thanks,

greg k-h

  reply	other threads:[~2007-09-12 12:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12  9:29 Andre Haupt
2007-09-12 12:02 ` Greg KH
2007-09-12 12:04   ` Greg KH
2007-09-12 12:07     ` Greg KH [this message]
2007-09-12 12:10       ` S.Çağlar Onur
2007-09-12 12:14       ` David Miller
2007-09-12 12:13     ` David Miller
2007-09-12 12:12   ` David Miller
2007-09-12 14:20     ` Coly Li
2007-09-12 14:26       ` Coly Li
2007-09-12 16:20     ` Marcel Holtmann
2007-09-12 12:16   ` Robert P. J. Day
2007-09-13 10:11 Toralf Förster
2007-09-13 12:29 ` Marcel Holtmann

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=20070912120726.GA13170@kroah.com \
    --to=greg@kroah.com \
    --cc=andre@finow14.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®