Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Mihaela Vitalariu <admiralwolverine@gmail.com>
Cc: Alsa-devel@alsa-project.org
Subject: Re: how do you people debug ALSA?
Date: Mon, 21 Jan 2008 09:39:51 -0600	[thread overview]
Message-ID: <4794BCC7.5070408@freescale.com> (raw)
In-Reply-To: <ef33e0240801210111l569c27f4k624d9b37dd33fce8@mail.gmail.com>

Mihaela Vitalariu wrote:
> Hello everyone!
> 
> How do you ALSA developers debug the ALSA code?

printk().

-- 
Timur Tabi
Linux kernel developer at Freescale

  parent reply	other threads:[~2008-01-21 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21  9:11 how do you people debug ALSA? Mihaela Vitalariu
2008-01-21 12:04 ` Jan-Benedict Glaw
2008-01-21 15:13   ` Mihaela Vitalariu
2008-01-21 15:39 ` Timur Tabi [this message]
2008-01-22 17:21   ` John Utz
  -- strict thread matches above, loose matches on Subject: below --
2008-01-21 20:25 mazarick
2008-01-22  8:45 ` Clemens Ladisch
2008-01-22 12:14 ` Claudio Matsuoka
2008-01-23 11:09 ` Takashi Iwai

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=4794BCC7.5070408@freescale.com \
    --to=timur@freescale.com \
    --cc=Alsa-devel@alsa-project.org \
    --cc=admiralwolverine@gmail.com \
    /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