From: "Frédéric DALLEAU" <frederic.dalleau@linux.intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/3] sco-tester: Update ECONNABORTED to EOPNOTSUPP
Date: Tue, 13 Aug 2013 15:10:24 +0200 [thread overview]
Message-ID: <520A3040.2090209@linux.intel.com> (raw)
In-Reply-To: <88BDC584-6DC7-457A-92B3-3C00D30CCEBC@holtmann.org>
Hi Marcel,
Le 13/08/2013 01:22, Marcel Holtmann a écrit :
> However I only looked at the error codes you listed in this email. Maybe there is even a better one, maybe there is not. I am pretty much open to discuss alternatives here.
Thanks for detailed feedback. For the vast majority of other errors
code, there was no need to go through code to eliminate them: Their
purpose if usually very restrictive.
Let's list some potential candidate just in case:
#define ENOSYS 38 /* Function not implemented */
#define ENOSR 63 /* Out of streams resources */
#define ENOMEDIUM 123 /* No medium found */
Regards,
Frederic
next prev parent reply other threads:[~2013-08-13 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 15:42 [PATCH 1/3] sco-tester: Update ECONNABORTED to EOPNOTSUPP Frédéric Dalleau
2013-08-09 15:42 ` [PATCH 2/3] sco-tester: Introduce adapter features Frédéric Dalleau
2013-09-09 8:33 ` Johan Hedberg
2013-09-09 12:54 ` Frédéric DALLEAU
2013-09-09 15:03 ` Johan Hedberg
2013-08-09 15:42 ` [PATCH 3/3] sco-tester: Test transparent data feature bit Frédéric Dalleau
2013-08-09 15:53 ` [PATCH 1/3] sco-tester: Update ECONNABORTED to EOPNOTSUPP Marcel Holtmann
2013-08-12 8:34 ` Frédéric DALLEAU
2013-08-12 23:22 ` Marcel Holtmann
2013-08-13 13:10 ` Frédéric DALLEAU [this message]
2013-09-02 15:53 ` Frédéric DALLEAU
2013-09-09 8:29 ` Johan Hedberg
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=520A3040.2090209@linux.intel.com \
--to=frederic.dalleau@linux.intel.com \
--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 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.