linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/4] android/client: Fix missing new line character
Date: Fri, 08 May 2015 15:03:28 +0200	[thread overview]
Message-ID: <2922399.uuX8CnvgJR@leonov> (raw)
In-Reply-To: <1430298953-31018-1-git-send-email-grzegorz.kolodziejczyk@tieto.com>

Hi Grzegorz,

On Wednesday 29 of April 2015 11:15:50 Grzegorz Kolodziejczyk wrote:
> New line character is missing for haltest_info. Without this logs are
> distorted after receiving configure mtu callback log.
> ---
>  android/client/if-gatt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/android/client/if-gatt.c b/android/client/if-gatt.c
> index 70287fc..e66cc20 100644
> --- a/android/client/if-gatt.c
> +++ b/android/client/if-gatt.c
> @@ -679,7 +679,7 @@ static void gattc_listen_cb(int status, int client_if)
>  /* Callback invoked when the MTU for a given connection changes */
>  static void gattc_configure_mtu_cb(int conn_id, int status, int mtu)
>  {
> -	haltest_info("%s: conn_id=%d, status=%d, mtu=%d", __func__, conn_id,
> +	haltest_info("%s: conn_id=%d, status=%d, mtu=%d\n", __func__, conn_id,
>  								status, mtu);
>  }

All patches applied, thanks.

-- 
BR
Szymon Janc

      parent reply	other threads:[~2015-05-08 13:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29  9:15 [PATCH 1/4] android/client: Fix missing new line character Grzegorz Kolodziejczyk
2015-04-29  9:15 ` [PATCH 2/4] android/gatt: Remove redundant comment line Grzegorz Kolodziejczyk
2015-04-29  9:15 ` [PATCH 3/4] android/gatt: Send notify mtu change for BR/EDR success conn Grzegorz Kolodziejczyk
2015-04-29  9:15 ` [PATCH 4/4] android/gatt: Fix updating mtu for no registered app Grzegorz Kolodziejczyk
2015-05-08 13:03 ` Szymon Janc [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=2922399.uuX8CnvgJR@leonov \
    --to=szymon.janc@tieto.com \
    --cc=grzegorz.kolodziejczyk@tieto.com \
    --cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).