From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000640]: azx code is nasty
Date: Wed, 10 Nov 2004 14:30:38 +0100 [thread overview]
Message-ID: <dfd63d078eae09c572eb23af577618f6@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=640>
======================================================================
Reported By: russell
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 640
Category: PCI - azx
Reproducibility: always
Severity: trivial
Priority: normal
Status: new
Distribution: Debian/Ubuntu
Kernel Version: 2.6.8.1
======================================================================
Date Submitted: 11-10-2004 14:30 CET
Last Modified: 11-10-2004 14:30 CET
======================================================================
Summary: azx code is nasty
Description:
Some of the code in the azx driver is very difficult to read, depending on
how you set up tabs etc in your IDE. This is a[n almost] purely cosmetic
change to codec_enum.c
I have commented out some of the snd_printdd()s inside the smaller helper
functions too (to make my poor l'il log look nicer). I have also changed
one obviously inefficient function (get_bit_value()) into a macro. All
seems to compile and work about as well as 1.0.7rc2 does (for me, not
particularly well - hence my work on it)
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
11-10-04 14:30 russell New Issue
11-10-04 14:30 russell File Added: codec_enum.c
11-10-04 14:30 russell Distribution => Debian/Ubuntu
11-10-04 14:30 russell Kernel Version => 2.6.8.1
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next reply other threads:[~2004-11-10 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 13:30 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-12 11:22 [ALSA - driver 0000640]: azx code is nasty bugtrack
2004-11-12 14:40 bugtrack
2004-12-08 18:54 bugtrack
2005-01-11 15:53 bugtrack
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=dfd63d078eae09c572eb23af577618f6@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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