From: John Bradford <john@grabjohn.com>
To: rmk@arm.linux.org.uk (Russell King)
Cc: fdavis@si.rr.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.59 : sound/oss/vidc.c
Date: Fri, 7 Feb 2003 20:03:55 +0000 (GMT) [thread overview]
Message-ID: <200302072003.h17K3t2U002303@darkstar.example.net> (raw)
In-Reply-To: <20030207194314.C30927@flint.arm.linux.org.uk> from "Russell King" at Feb 07, 2003 07:43:14 PM
> > --- linux/sound/oss/vidc.c.old 2003-01-16 21:21:38.000000000 -0500
> > +++ linux/sound/oss/vidc.c 2003-02-07 02:59:44.000000000 -0500
> > @@ -225,7 +225,7 @@
> > newsize = 208;
> > if (newsize > 4096)
> > newsize = 4096;
> > - for (new2size = 128; new2size < newsize; new2size <<= 1);
> > + for (new2size = 128; new2size < newsize; new2size <<= 1)
> > if (new2size - newsize > newsize - (new2size >> 1))
> > new2size >>= 1;
> > if (new2size > 4096) {
>
> The code is correct as it originally stood.
>
> It looks like indent has a bug and incorrectly formats this to look wrong.
> Back in 2.2 times, the code looks like this:
>
> for (new2size = 128; new2size < newsize; new2size <<= 1);
> if (new2size - newsize > newsize - (new2size >> 1))
> new2size >>= 1;
>
> and this is the intended functionality. Please do NOT apply the patch.
I thought we were switching to negative tab indentation, anyway:
http://marc.theaimsgroup.com/?l=linux-kernel&m=104125431009832&w=2
:-)
John.
next prev parent reply other threads:[~2003-02-07 19:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 17:13 [PATCH] 2.5.59 : sound/oss/vidc.c Frank Davis
2003-02-07 19:43 ` Russell King
2003-02-07 20:03 ` John Bradford [this message]
2003-02-07 20:47 ` Richard B. Johnson
2003-02-07 21:58 ` J.A. Magallon
2003-02-07 22:20 ` Russell King
2003-02-07 22:35 ` John Bradford
2003-02-10 22:03 ` Bill Davidsen
2003-02-11 7:49 ` Horst von Brand
2003-02-07 23:54 ` Alan Cox
2003-02-10 0:23 ` Rusty Russell
2003-02-08 0:37 Alexei Podtelezhnikov
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=200302072003.h17K3t2U002303@darkstar.example.net \
--to=john@grabjohn.com \
--cc=fdavis@si.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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).