public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 17:18:44 +0200	[thread overview]
Message-ID: <200901051718.44559.siarhei.siamashka@nokia.com> (raw)
In-Reply-To: <002701c96f43$dc833c90$9589b5b0$@de>

On Monday 05 January 2009 16:42:39 ext Christian Hoene wrote:
> > There are some parts that look a bit redundant/suspicious:
> > > @@ -47,7 +47,7 @@ static ssize_t __read(int fd, void *buf, size_t
> > > count) while (count > 0) {
> > >                 len = read(fd, buf + pos, count);
> > >                 if (len <= 0)
> > > -                       return len;
> > > +                       return pos > len ? pos : len;
> > >
> > >                 count -= len;
> > >                 pos   += len;
> >
> > Is the ternary '?' operator really needed here? In this part of code we
> > know for sure that 'len' is less or equal to zero, also 'pos ' is a
> > positive number or zero. Having just 'return pos' should be enough.
>
> No. If read returns an error, the this error is passed to __read, too.

I mean that 'return pos > len ? pos : len' and 'return pos' expressions are
completely interexchangeable in this context.

Regarding this particular change itself, was there a reproducible problem in
your testing that strictly required this fix? Was it involving sockets or
pipes?

But the bug in 'sbc_get_codesize' is the unquestionable one for sure. Good job
finding and fixing it.

-- 
Best regards,
Siarhei Siamashka

  reply	other threads:[~2009-01-05 15:18 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 [this message]
2009-01-05 15:24                 ` Siarhei Siamashka
2009-01-05 15:33                 ` Christian Hoene
2009-01-05 17:39                   ` Siarhei Siamashka
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=200901051718.44559.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