All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bccmd patch
Date: Mon, 19 Jun 2006 20:09:04 +0200	[thread overview]
Message-ID: <1150740544.4277.28.camel@localhost> (raw)
In-Reply-To: <70DCB28C5BB04A4BBB1C8512589BAC65E69930@MAIL006.mail.lan>

Hi Chris,

> I didn't see any response to this patch - resending to ensure that it
> didn't get missed.
> 
> I discovered a couple of things :
> 1. bccmd has some nice features that aren't mentioned in its "usages".
> 2. bccmd psset didn't work for keys with a size > 32 bits (because the
> OPT_PSKEY macro returned an error if you specified more than one value
> for the key, but it expected a list of bytes if the length is more than
> 1 or 2).
>  
> Here's a patch (against bluez-utils version 2.25) :

please create a patch against the latest CVS (or bluez-utils-3.1) and
attach it. Your mail client is messing up whitespaces and newlines.

Regards

Marcel




_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-06-19 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 16:16 [Bluez-users] Bccmd patch Brand, Chris
2006-06-19 18:09 ` Marcel Holtmann [this message]
2006-06-19 18:32   ` Brand, Chris
2006-06-20  9:50     ` Marcel Holtmann
2006-06-20 12:08       ` Sumeet VERMA
2006-06-20 18:19       ` Brand, Chris
2006-06-26 12:23         ` Marcel Holtmann
2006-07-05 18:46           ` [Bluez-users] [PATCH] " Brand, Chris
2006-07-13 16:13           ` [Bluez-users] [PATCH] Bccmd patch - resend Brand, Chris
  -- strict thread matches above, loose matches on Subject: below --
2006-04-13 20:40 [Bluez-users] Bccmd patch Brand, Chris

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=1150740544.4277.28.camel@localhost \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.