linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Syam Sidhardhan <s.syam@samsung.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 2/2] gdbus: Replace leading spaces with tabs
Date: Fri, 16 Nov 2012 10:07:23 +0200	[thread overview]
Message-ID: <20121116080723.GB9653@x220> (raw)
In-Reply-To: <1351000626-22632-2-git-send-email-s.syam@samsung.com>

Hi Syam,

On Tue, Oct 23, 2012, Syam Sidhardhan wrote:
> Trivial formatting fix.
> ---
>  gdbus/object.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)

This patch has been applied. Thanks.

Johan

  reply	other threads:[~2012-11-16  8:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 13:57 [PATCH BlueZ 1/2] audio: Fix headset NULL pointer dereference during AT+BLDN response Syam Sidhardhan
2012-10-23 13:57 ` [PATCH BlueZ 2/2] gdbus: Replace leading spaces with tabs Syam Sidhardhan
2012-11-16  8:07   ` Johan Hedberg [this message]
2012-11-09  3:32 ` [PATCH BlueZ 1/2] audio: Fix headset NULL pointer dereference during AT+BLDN response Syam Sidhardhan
2012-11-13 15:40   ` Johan Hedberg
2012-11-13 16:27     ` Syam Sidhardhan

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=20121116080723.GB9653@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=s.syam@samsung.com \
    /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).