From: Bastien Nocera <hadess@hadess.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Add udev rules to start bluetooth on-demand
Date: Wed, 24 Jun 2009 17:52:56 +0100 [thread overview]
Message-ID: <1245862376.26486.17217.camel@localhost.localdomain> (raw)
In-Reply-To: <1245862000.15367.146.camel@violet>
On Wed, 2009-06-24 at 18:46 +0200, Marcel Holtmann wrote:
> Hi Bastien,
>
> > > > > > > > As discussed in previous mails.
> > > > > > >
> > > > > > > please name it bluetooth.rules. The daemon is also called bluetoothd and
> > > > > > > not bluezd.
> > > > > > >
> > > > > > > Also you need to have the EXTRA_DIST part in it since _DATA doesn't get
> > > > > > > added to the distribution automatically. For all this changes, you have
> > > > > > > to check with make distcheck.
> > > > > >
> > > > > > Fixed version attached
> > > > >
> > > > > we might need to put this into ifndef INITSCRIPTS since it makes no
> > > > > sense to install the init script and the udev rule at the same time.
> > > >
> > > > Revised patch attached
> > >
> > > +
> > > +if INISCRIPTS
> > > +else
> > > +rules_DATA += bluetooth.rules
> > > endif
> >
> > ifndef isn't an automake construct.
> >
>
> then if !INITSCRIPTS should do it. However I was more asking about the
> spelling mistake. You forgot a T ;)
Well, that's embarrassing...
next prev parent reply other threads:[~2009-06-24 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 13:39 [PATCH] Add udev rules to start bluetooth on-demand Bastien Nocera
2009-06-21 13:50 ` Marcel Holtmann
2009-06-21 14:05 ` Bastien Nocera
2009-06-21 14:10 ` Marcel Holtmann
2009-06-24 11:35 ` Bastien Nocera
2009-06-24 16:43 ` Marcel Holtmann
2009-06-24 16:44 ` Bastien Nocera
2009-06-24 16:46 ` Marcel Holtmann
2009-06-24 16:52 ` Bastien Nocera [this message]
2009-06-27 10:27 ` Marcel Holtmann
2009-06-29 15:03 ` Bastien Nocera
2009-06-30 1:07 ` 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=1245862376.26486.17217.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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