All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
To: ext-jukka.hynninen@vaisala.com
Cc: alsa-devel@alsa-project.org, broonie@sirena.org.uk
Subject: Re: ASoC: Merging at91 and avr32 dirs - test report
Date: Mon, 27 Oct 2008 10:57:43 +0100	[thread overview]
Message-ID: <49059097.5020309@atmel.com> (raw)
In-Reply-To: <B9D3C48C98930741A166756A50C44A610F17B565@helx1.corp.vaisala.com>

Hi,
ext-jukka.hynninen@vaisala.com a écrit :
> Quoting Mark Brown:
> 
>>> This is propably a false alarm, exactly the same happens with
> at91-ssc.c
>> OK, so you're happy that the new and old AT91 drivers perform
>> equivalently?
> 
> Life's full of small joys
> 
>> present in current ASoC.  The patch below is *entirely* untested but
> may
>> help.  It needs more thought and (obviously) testing to make sure it's
>> safe before it can be merged.
> 
> Thanks, works like a charm. I'll put the patch on a test.
> 
> 
> -Jukka
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 
I am writing to know what is the current status about the at91/avr32 
merging?
Is there any progress concerning the testing?
What is required for the patch to be accepted?

Regards,
Sedji

  reply	other threads:[~2008-10-27  9:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 15:15 ASoC: Merging at91 and avr32 dirs - test report ext-jukka.hynninen
2008-10-10 18:53 ` Mark Brown
2008-10-14  7:28   ` ext-jukka.hynninen
2008-10-14 12:38     ` ext-jukka.hynninen
2008-10-14 12:58       ` Mark Brown
2008-10-14 14:00         ` ext-jukka.hynninen
2008-10-27  9:57           ` Sedji Gaouaou [this message]
2008-10-27 10:42             ` Mark Brown
2008-10-27 11:13               ` ext-jukka.hynninen
2008-10-27 11:29                 ` Mark Brown
2008-10-27 13:34                   ` ext-jukka.hynninen
2008-10-13 14:22 ` Sedji Gaouaou
2008-10-13 14:34   ` Mark Brown

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=49059097.5020309@atmel.com \
    --to=sedji.gaouaou@atmel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=ext-jukka.hynninen@vaisala.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 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.