Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] missing <linux/limits.h> include in storage.c	and hcitool.c
Date: Fri, 22 Apr 2005 13:53:33 +0200	[thread overview]
Message-ID: <1114170813.32265.68.camel@pegasus> (raw)
In-Reply-To: <4268E475.8060807@gmx.ch>

Hi Marco,

> > this can't be, because we don't include header files from the kernel and
> > so <linux/*> and <asm/*> are taboo.
> 
> I'm sorry. I should have mentioned that PATH_MAX is missing.
> that would have been helpful...

actually I thought that I addressed that :(

> > Does simply including <limits.h> is also working?
> 
> I checked the available headers. looks like sys/param.h is the choice.
> (But just because it includes <linux/limits.h>)

Patch for it is now in the CVS.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-04-22 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22 11:16 [Bluez-users] missing <linux/limits.h> include in storage.c and hcitool.c Marco Trudel
2005-04-22 11:22 ` Marcel Holtmann
2005-04-22 11:48   ` Marco Trudel
2005-04-22 11:53     ` Marcel Holtmann [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=1114170813.32265.68.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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