public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <mulix@mulix.org>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org, akpm@zip.com.au
Subject: Re: [CFT/PATCH] give sound/oss/trident a holiday cleanup for 2.6
Date: Fri, 2 Jan 2004 02:12:04 +0200	[thread overview]
Message-ID: <20040102001203.GD1718@actcom.co.il> (raw)
In-Reply-To: <20040101160420.6a326d0a.akpm@osdl.org>

On Thu, Jan 01, 2004 at 04:04:20PM -0800, Andrew Morton wrote:

> hmm, how come a whitespace cleanup patch adds nearly 200 lines which have
> trailing whitespace?

That would be either xemacs's or indent's fault. Can't be my
fault. No sir. Anyway, unless whitespace-mode is lying to me now, no
line has more than at most one character of whitespace added. If it
bugs you, I'll clean it up - it's a slow night tonight ;-) 

> >  All of the non-indentation changes are in the
> >  trident-cleanup-fixes-D1-2.6.0 patch, attached here inline. It needs
> >  the indentation patch to be applied before it to apply
> >  cleanly. Compiles, boots and plays music fine. Patch is against
> >  2.6.0. Andrew, please add these two patches to -mm1 instead of the
> >  "humongopatch" currently there. Thanks! 
> 
> Could we please have a description of the substantive changes in
> this patch?

Sure thing: 

- switch lock_set_fmt() and unlock_set_fmt() from macros to inline
functions. Macros that call return() are EVIL.
- simplify lock_set_fmt() and implement it via test_and_set_bit()
rather than a spinlock protecting an int.
- fix a bug wherein we would do an up() on a semaphore that hasn't
been down()ed if a signal happened after timeout in trident_write().
- fix a bug where we would not release the open_sem on OOM.
- make the arguments for prog_dmabuf clearer (int -> enum), and add
two wrapper functions around it, one for record and one for playback. 
- fix a bug where we would call VALIDATE_STATE after
lock_kernel(). Since VALIDATE_STATE does 'return' if validation fails,
bad things can happen. Thanks to Dawson Engler <engler@stanford.edu>
and the Stanford checker for spotting.
- remove the calls to lock_kernel() from trident_release() and
trident_mmap(). trident_release() appears to be covered by the
open_sem, and trident_mmap() is covered by state->sem.
- s/TRUE/1/, s/FALSE/0/

> Thanks.

Entirely my pleasure. 

Cheers, 
Muli 
-- 
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/

"the nucleus of linux oscillates my world" - gccbot@#offtopic


  reply	other threads:[~2004-01-02  0:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-29 18:38 [CFT/PATCH] give sound/oss/trident a holiday cleanup for 2.6 Muli Ben-Yehuda
2003-12-29 18:50 ` Linus Torvalds
2003-12-29 18:56   ` Muli Ben-Yehuda
2003-12-29 19:09     ` Jeff Garzik
2003-12-29 19:40       ` Linus Torvalds
2003-12-29 20:32         ` Jeff Garzik
2004-01-01 23:51   ` Muli Ben-Yehuda
2004-01-02  0:04     ` Andrew Morton
2004-01-02  0:12       ` Muli Ben-Yehuda [this message]
2004-01-02  0:26         ` Andrew Morton
2004-01-02  0:39           ` Mike Fedyk
2004-01-02  0:43             ` Andrew Morton
2003-12-29 18:53 ` Mike Fedyk

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=20040102001203.GD1718@actcom.co.il \
    --to=mulix@mulix.org \
    --cc=akpm@osdl.org \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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