All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, kernel@avr32linux.org
Subject: Re: [PATCH 2/2] ALSA sound driver for	the	AT73C213	DAC	using Atmel SSC driver
Date: Mon, 16 Jul 2007 16:46:58 +0200	[thread overview]
Message-ID: <1184597218.15535.36.camel@localhost.localdomain> (raw)
In-Reply-To: <s5h4pk4za3q.wl%tiwai@suse.de>


On Mon, 2007-07-16 at 16:39 +0200, Takashi Iwai wrote:
> At Mon, 16 Jul 2007 16:30:56 +0200,
> I wrote:
> > 
> > At Mon, 16 Jul 2007 16:25:28 +0200,
> > Hans-Christian Egtvedt wrote:
> > > 
> > > 
> > > On Mon, 2007-07-16 at 16:15 +0200, Takashi Iwai wrote:
> > > > At Mon, 16 Jul 2007 16:14:59 +0200,
> > > > Hans-Christian Egtvedt wrote:

<cut driver description>

> > > > Are these intended to be merged to 2.6.23 kernel?
> > > 
> > > I would prefer that yes. AFAIK alsa-devel@ is the correct list for the
> > > sound drivers?
> > 
> > Yes.  Then the questions are:
> > - the driver is mature enough for the upstream merge,
> > - whether it's built and tested on the latest 2.6.22 (or more
> >   prefarably on the latest git) tree
> 
> Also,
> 
> - whether atmel-ssc driver would be merged to 2.6.23, too
>   (otherwise it makes no sense to merge only the corresponding ALSA
>    driver)

Agree, I have no feedback on the atmel-ssc driver yet. It should be a
trivial addition the the kernel.

-- 
With kind regards,

Hans-Christian Egtvedt, siv.ing. (M.Sc.)
Applications Engineer - AVR32 System Solutions - Atmel Norway

  reply	other threads:[~2007-07-16 14:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 14:14 [PATCH 1/2] Add SPI devices to ALSA Kconfig and Makefile Hans-Christian Egtvedt
2007-07-16 14:14 ` [PATCH 2/2] ALSA sound driver for the AT73C213 DAC using Atmel SSC driver Hans-Christian Egtvedt
2007-07-16 14:15   ` Takashi Iwai
2007-07-16 14:25     ` Hans-Christian Egtvedt
2007-07-16 14:30       ` Takashi Iwai
2007-07-16 14:39         ` Takashi Iwai
2007-07-16 14:46           ` Hans-Christian Egtvedt [this message]
2007-07-16 14:47             ` Takashi Iwai
2007-07-16 14:43         ` Hans-Christian Egtvedt
2007-07-16 14:48           ` Takashi Iwai
2007-07-16 15:08   ` Takashi Iwai
2007-07-16 15:27     ` Haavard Skinnemoen
2007-07-16 15:32       ` Takashi Iwai
2007-07-17  8:37     ` Hans-Christian Egtvedt
2007-07-17  8:48       ` Haavard Skinnemoen
2007-07-17  8:54         ` Hans-Christian Egtvedt
2007-07-17 10:23           ` Takashi Iwai
2007-07-17 11:23             ` Hans-Christian Egtvedt
2007-07-17 11:36               ` Haavard Skinnemoen
2007-07-23 14:49             ` Takashi Iwai
2007-07-26  6:21               ` Hans-Christian Egtvedt

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=1184597218.15535.36.camel@localhost.localdomain \
    --to=hcegtvedt@atmel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kernel@avr32linux.org \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.