Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Ehle <azverkan@yahoo.com>
To: alsa-devel@alsa-project.org
Subject: Status of the alsa sbxfi driver
Date: Sun, 1 Mar 2009 13:37:27 -0800	[thread overview]
Message-ID: <3c5a513f0903011337o5e3b4686ha985c4e73e75e990@mail.gmail.com> (raw)

I merged the topic/sbxfi branch from
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
into my latest 2.6.29-rc6 build.  I've done a few quick tests and I
have not run into any issues so far (except the driver has an
excessive amount of kprintfs).  Is this the latest version of the
sbxfi driver?

>From following the alsa-devel list and the git tree above, there
doesn't seem to be any changes since Oct 30 or so.  What work needs to
be done to get this driver into a state where it could be pushed to
the main alsa git and eventually to Linus' tree?

             reply	other threads:[~2009-03-01 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01 21:37 Brandon Ehle [this message]
2009-03-02 11:36 ` Status of the alsa sbxfi driver 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=3c5a513f0903011337o5e3b4686ha985c4e73e75e990@mail.gmail.com \
    --to=azverkan@yahoo.com \
    --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