Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@gmail.com>
To: Szymon Janc <szymon.janc@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] android/avdtp: Constify data in avdtp_service_cap_new
Date: Thu, 28 Aug 2014 20:25:36 +0200	[thread overview]
Message-ID: <1950624.rjRFFKmpIc@athlon> (raw)
In-Reply-To: <1409144479-13862-1-git-send-email-szymon.janc@tieto.com>

On Wednesday 27 August 2014 15:01:19 Szymon Janc wrote:
> ---
>  android/avdtp.c | 3 ++-
>  android/avdtp.h | 3 ++-
>  2 files changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/android/avdtp.c b/android/avdtp.c
> index 3985fb3..074ca13 100644
> --- a/android/avdtp.c
> +++ b/android/avdtp.c
> @@ -2960,7 +2960,8 @@ struct avdtp_service_capability
> *avdtp_get_codec(struct avdtp_remote_sep *sep) }
> 
>  struct avdtp_service_capability *avdtp_service_cap_new(uint8_t category,
> -							void *data, int length)
> +							const void *data,
> +							int length)
>  {
>  	struct avdtp_service_capability *cap;
> 
> diff --git a/android/avdtp.h b/android/avdtp.h
> index 28895ea..d5335e4 100644
> --- a/android/avdtp.h
> +++ b/android/avdtp.h
> @@ -218,7 +218,8 @@ void avdtp_unref(struct avdtp *session);
>  struct avdtp *avdtp_ref(struct avdtp *session);
> 
>  struct avdtp_service_capability *avdtp_service_cap_new(uint8_t category,
> -							void *data, int size);
> +							const void *data,
> +							int size);
> 
>  struct avdtp_service_capability *avdtp_get_codec(struct avdtp_remote_sep
> *sep);

Applied.

-- 
Szymon K. Janc
szymon.janc@gmail.com

      reply	other threads:[~2014-08-28 18:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 13:01 [PATCH] android/avdtp: Constify data in avdtp_service_cap_new Szymon Janc
2014-08-28 18:25 ` 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=1950624.rjRFFKmpIc@athlon \
    --to=szymon.janc@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=szymon.janc@tieto.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