From: Siarhei Siamashka <siarhei.siamashka@nokia.com>
To: "ext Christian Hoene" <hoene@uni-tuebingen.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] SBC Encoder program
Date: Mon, 5 Jan 2009 19:39:23 +0200 [thread overview]
Message-ID: <200901051939.23341.siarhei.siamashka@nokia.com> (raw)
In-Reply-To: <004501c96f4a$ea4f0500$beed0f00$@de>
On Monday 05 January 2009 17:33:10 ext Christian Hoene wrote:
> > I mean that 'return pos > len ? pos : len' and 'return pos' expressions
> > are completely interexchangeable in this context.
>
> They are slightly different but really, I do not care. Both fixes will work.
Yes, because they provide exactly identical results :-) In this sense, your
fix is a bit broken, because it will never allow to pass through and return a
negative error code.
> At least one must be applied. BTW: Why not use fread instead? ;-)
Agreed here. What's the point of having double underscored versions (such
identifiers are reserved and not allowed to be used by programs) of read and
write functions? Maybe they can be purged and just normal read/write calls
could be used instead? Or alternatively fread/fwrite indeed?
Also there seems to be a performance issue: memove calls are redundant and
can be avoided in SBC encoder program.
I can confirm that getting rid of the __read and __write functions (or fixing
them with your patch or its modification) is the only change, needed to pass
encoder test 08.
All the other changes are not directly related to this particular testcase,
though a fix for 'codesize' is also nice to have. It would be required for a
faster, memmove-free version of the encoder.
You have found and fixed two definite bugs (as I can see it now), that's very
good. Now it would be nice to apply the fixes to git with the descriptive
commit messages and move forward ;-)
--
Best regards,
Siarhei Siamashka
next prev parent reply other threads:[~2009-01-05 17:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812301246.25781.siarhei.siamashka@nokia.com>
2009-01-01 14:24 ` SBC encoder conformance test for version 4.25 passed! Christian Hoene
2009-01-05 8:27 ` Siarhei Siamashka
2009-01-05 11:43 ` [PATCH] SBC Encoder program Christian Hoene
2009-01-05 12:22 ` Luiz Augusto von Dentz
2009-01-05 12:28 ` Christian Hoene
2009-01-05 13:13 ` Luiz Augusto von Dentz
2009-01-05 14:42 ` Christian Hoene
2009-01-05 14:48 ` Siarhei Siamashka
2009-01-05 13:22 ` Siarhei Siamashka
2009-01-05 14:42 ` Christian Hoene
2009-01-05 15:18 ` Siarhei Siamashka
2009-01-05 15:24 ` Siarhei Siamashka
2009-01-05 15:33 ` Christian Hoene
2009-01-05 17:39 ` Siarhei Siamashka [this message]
2009-01-05 19:45 ` Marcin Tolysz
2009-01-05 21:11 ` David Sainty
2009-01-05 20:36 ` Marcin Tolysz
2009-01-06 2:43 ` Marcel Holtmann
2009-01-05 12:53 ` SBC encoder conformance test for version 4.25 passed! Luiz Augusto von Dentz
2009-07-15 14:49 ` Is it possible that user change a stream path between Speaker and Bluetooth like normal phone? Chan-Yeol Park
2009-07-15 15:27 ` Bastien Nocera
2009-01-05 14:55 ` SBC encoder conformance test for version 4.25 passed! Christian Hoene
2009-01-05 15:32 ` Siarhei Siamashka
2009-01-06 0:40 ` Nick Pelly
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=200901051939.23341.siarhei.siamashka@nokia.com \
--to=siarhei.siamashka@nokia.com \
--cc=hoene@uni-tuebingen.de \
--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