Linux bluetooth development
 help / color / mirror / Atom feed
From: Gustavo Padovan <padovan@profusion.mobi>
To: ilia.kolominsky@gmail.com
Cc: linux-bluetooth@vger.kernel.org, Ilia Kolomisnky <iliak@ti.com>
Subject: Re: [PATCH Bluetooth-next v2] Fixes l2cap "command reject" reply according to spec.
Date: Thu, 7 Jul 2011 15:26:33 -0300	[thread overview]
Message-ID: <20110707182633.GB16322@joana> (raw)
In-Reply-To: <1310009762-18032-1-git-send-email-iliak@ti.com>

* ilia.kolominsky@gmail.com <ilia.kolominsky@gmail.com> [2011-07-07 06:36:02 +0300]:

> From: Ilia Kolomisnky <iliak@ti.com>
> 
> There can 3 reasons for the "command reject" reply produced
> by the stack. Each such reply should be accompanied by the
> relevand data ( as defined in spec. ). Currently there is one
> instance of "command reject" reply with reason "invalid cid"
> wich is fixed. Also, added clean-up definitions related to the
> "command reject" replies.
> 
> Signed-off-by: Ilia Kolomisnky <iliak@ti.com>
> ---
>  include/net/bluetooth/l2cap.h |   19 ++++++++++++++++++-
>  net/bluetooth/l2cap_core.c    |   15 +++++++++------
>  2 files changed, 27 insertions(+), 7 deletions(-)

Patch doesn't apply to bluetooth-next

Applying: Fixes l2cap "command reject" reply according to spec.
fatal: corrupt patch at line 62
Patch failed at 0001 Fixes l2cap "command reject" reply according to spec.
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".

	Gustavo

      reply	other threads:[~2011-07-07 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07  3:36 [PATCH Bluetooth-next v2] Fixes l2cap "command reject" reply according to spec ilia.kolominsky
2011-07-07 18:26 ` Gustavo Padovan [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=20110707182633.GB16322@joana \
    --to=padovan@profusion.mobi \
    --cc=ilia.kolominsky@gmail.com \
    --cc=iliak@ti.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