Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Mikel Astiz <mikel.astiz.oss@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: Re: [PATCH BlueZ v0] doc: Fix optional properties not marked as such
Date: Thu, 25 Apr 2013 10:38:17 +0300	[thread overview]
Message-ID: <20130425073817.GA9094@x220> (raw)
In-Reply-To: <1366875235-12077-1-git-send-email-mikel.astiz.oss@gmail.com>

Hi Mikel,

On Thu, Apr 25, 2013, Mikel Astiz wrote:
> Commit 826023de56896e83f35ae69a73d6a120a2f5b11e made some of the
> device's properties optional but the documentation was not updated
> accordingly. More specifically, the properties 'Name' and 'UUIDs' won't
> be present if the information is not available.
> ---
>  doc/device-api.txt | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Applied. Thanks.

Johan

      reply	other threads:[~2013-04-25  7:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25  7:33 [PATCH BlueZ v0] doc: Fix optional properties not marked as such Mikel Astiz
2013-04-25  7:38 ` Johan Hedberg [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=20130425073817.GA9094@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mikel.astiz.oss@gmail.com \
    --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