Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Timur Tabi <timur@freescale.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] Fix register programming in Freescale MPC8610 HPCD sound driver
Date: Mon, 23 Jun 2008 18:51:15 +0200	[thread overview]
Message-ID: <s5hbq1s3xj0.wl%tiwai@suse.de> (raw)
In-Reply-To: <s5hej6o3xqs.wl%tiwai@suse.de>

At Mon, 23 Jun 2008 18:46:35 +0200,
I wrote:
> 
> At Mon, 23 Jun 2008 11:41:13 -0500,
> Timur Tabi wrote:
> > 
> > Timur Tabi wrote:
> > > Fix the Freescale MPC8610 HPCD sound driver so that it programs the DMACR
> > > and PMUXCR registers in the global utilities correctly.
> > > 
> > > Signed-off-by: Timur Tabi <timur@freescale.com>
> > > ---
> > > 
> > > This patch is for 2.6.26.  A similar fix has already been made in the ASOC V2
> > > repository.  
> > 
> > Is this patch going to get picked up for 2.6.26?  I posted it 10 days ago, but
> > it looks like no one noticed.
> 
> No, it's not pushed for 2.6.26 although it's already on my tree for
> the next kernel release.  If this is an urgent fix for 2.6.26, please
> show it explicitly.  Otherwise I won't do it always (especially
> changes for ASoC that I cannot test by myself)...

Well, let me clarify a bit more: if the patch should be *merged* to
2.6.26 tree, this has to be noted somewhere.  The text "the patch is
for 2.6.26" can be understood (as I did so indeed) like that "the
patch can be applied cleanly to 2.6.26".


Takashi

  parent reply	other threads:[~2008-06-23 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 19:02 [PATCH] Fix register programming in Freescale MPC8610 HPCD sound driver Timur Tabi
2008-06-13 19:34 ` Liam Girdwood
2008-06-23 16:41 ` Timur Tabi
2008-06-23 16:46   ` Takashi Iwai
2008-06-23 16:48     ` Timur Tabi
2008-06-23 16:57       ` Takashi Iwai
2008-06-23 16:59         ` Timur Tabi
2008-06-23 17:03           ` Takashi Iwai
2008-06-23 16:51     ` Takashi Iwai [this message]
2008-06-23 16:55       ` Timur Tabi

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=s5hbq1s3xj0.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=timur@freescale.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