From: Mikel Astiz <mikel.astiz.oss@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: Re: [RFC BlueZ v0 2/5] Use defines instead of magic numbers
Date: Wed, 18 Jul 2012 13:49:47 +0200 [thread overview]
Message-ID: <CANT-zCVAm80TqiVy=mnW0j4jMYDaitFR6GZ7qBWLAvuH+BQ2PQ@mail.gmail.com> (raw)
In-Reply-To: <1337009584-17181-3-git-send-email-mikel.astiz.oss@gmail.com>
Hi,
On Mon, May 14, 2012 at 5:33 PM, Mikel Astiz <mikel.astiz.oss@gmail.com> wrote:
> From: Mikel Astiz <mikel.astiz@bmw-carit.de>
>
> The error-handling code should use the defines instead of magic numbers.
> ---
> src/device.c | 42 +++++++++++++++++++++---------------------
> 1 files changed, 21 insertions(+), 21 deletions(-)
Ping.
This was included inside a RFC series but has actually no dependency.
Cheers,
Mikel
next prev parent reply other threads:[~2012-07-18 11:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 15:32 [RFC BlueZ v0 0/5] ACL disconnect reason Mikel Astiz
2012-05-14 15:33 ` [RFC BlueZ v0 1/5] doc: Add D-Bus signal to provide " Mikel Astiz
2012-05-14 15:33 ` [RFC BlueZ v0 2/5] Use defines instead of magic numbers Mikel Astiz
2012-07-18 11:49 ` Mikel Astiz [this message]
2012-07-18 12:23 ` Johan Hedberg
2012-05-14 15:33 ` [RFC BlueZ v0 3/5] Propagate disconnect reason to adapter Mikel Astiz
2012-05-14 15:33 ` [RFC BlueZ v0 4/5] Propagate disconnect reason to device Mikel Astiz
2012-05-14 15:33 ` [RFC BlueZ v0 5/5] Send D-Bus signal to propagate disconnect reason Mikel Astiz
2012-05-14 17:00 ` [RFC BlueZ v0 0/5] ACL " Luiz Augusto von Dentz
2012-05-15 6:46 ` Mikel Astiz
2012-05-15 8:10 ` Luiz Augusto von Dentz
2012-05-15 8:45 ` Mikel Astiz
2012-05-15 9:58 ` Luiz Augusto von Dentz
2012-05-16 7:12 ` Mikel Astiz
2012-05-16 14:28 ` Mike
2012-05-17 13:41 ` Luiz Augusto von Dentz
2012-05-17 14:00 ` Mike
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='CANT-zCVAm80TqiVy=mnW0j4jMYDaitFR6GZ7qBWLAvuH+BQ2PQ@mail.gmail.com' \
--to=mikel.astiz.oss@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mikel.astiz@bmw-carit.de \
/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;
as well as URLs for NNTP newsgroup(s).