From: Gustavo Padovan <gustavo@padovan.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fix error handling for HCI socket options
Date: Sun, 1 Sep 2013 17:21:01 +0100 [thread overview]
Message-ID: <20130901162101.GG7440@joana> (raw)
In-Reply-To: <1377534579-5781-1-git-send-email-marcel@holtmann.org>
Hi Marcel,
2013-08-26 Marcel Holtmann <marcel@holtmann.org>:
> The HCI sockets for monitor and control do not support any HCI specific
> socket options and if tried, an error will be returned. However the
> error used is EINVAL and that is not really descriptive. To make it
> clear that these sockets are not handling HCI socket options, return
> EBADFD instead.
>
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> ---
> net/bluetooth/hci_sock.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Patch has been applied to bluetooth-next. Thanks.
Gustavo
prev parent reply other threads:[~2013-09-01 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 16:29 [PATCH] Bluetooth: Fix error handling for HCI socket options Marcel Holtmann
2013-09-01 16:21 ` 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=20130901162101.GG7440@joana \
--to=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).