All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Radoslaw Jablonski <radoslawjablonski@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH obexd] Use 'nice abort' when canceling outgoing OPP transer
Date: Mon, 8 Aug 2011 15:40:14 +0300	[thread overview]
Message-ID: <20110808124014.GA21425@dell> (raw)
In-Reply-To: <1312804898-4117-1-git-send-email-radoslawjablonski@gmail.com>

Hi Radek,

On Mon, Aug 08, 2011, Radoslaw Jablonski wrote:
> Previously client was suddenly disconnecting to cancel
> outgoing OPP transfer. Now ABORT command will be sent
> before disconnecting with server in that scenario.
> 
> This change is required to pass TC_CLIENT_OPH_BV_27_I PTS
> test case (not mandatory for qualification).
> ---
>  Makefile.am |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Makefile.am b/Makefile.am
> index d412f02..009bab3 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -142,7 +142,7 @@ service_DATA = $(service_in_files:.service.in=.service)
>  AM_CFLAGS = @OPENOBEX_CFLAGS@ @BLUEZ_CFLAGS@ @EBOOK_CFLAGS@ \
>  			@GTHREAD_CFLAGS@ @GLIB_CFLAGS@ @DBUS_CFLAGS@ \
>  			@LIBICAL_CFLAGS@ -D_FILE_OFFSET_BITS=64 \
> -			@TRACKER_CFLAGS@ \
> +			@TRACKER_CFLAGS@ -DUSE_NICE_ABORT \
>  			-DOBEX_PLUGIN_BUILTIN -DPLUGINDIR=\""$(plugindir)"\"
>  
>  INCLUDES = -I$(builddir)/src -I$(srcdir)/src -I$(srcdir)/plugins \

Could you instead just remove the whole #ifdef section from obex_xfer.c
and make "nice abort" the only option that doesn't need separately
enabling. There's no reason to keep the non-nice abort around anymore.
It was only there since ancient versions of OpenOBEX didn't support
proper abort.

Johan

      reply	other threads:[~2011-08-08 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 12:01 [PATCH obexd] Use 'nice abort' when canceling outgoing OPP transer Radoslaw Jablonski
2011-08-08 12:40 ` 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=20110808124014.GA21425@dell \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=radoslawjablonski@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.