All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Jiri Slaby <jslaby@suse.cz>
Cc: v1ron@mail.ru, Greg KH <gregkh@linuxfoundation.org>,
	stable <stable@vger.kernel.org>, Takashi Iwai <tiwai@suse.de>
Subject: Re: ALSA: oxygen stable commit difference
Date: Fri, 15 May 2015 22:40:54 +0200	[thread overview]
Message-ID: <555659D6.8090601@ladisch.de> (raw)
In-Reply-To: <55560015.9080604@suse.cz>

Jiri Slaby wrote:
> This:
> commit 1f91ecc14deea9461aca93273d78871ec4d98fcd
> Author: Roman Volkov <v1ron@mail.ru>
> Date:   Fri Jan 24 16:18:11 2014 +0400
>
>     ALSA: oxygen: modify adjust_dg_dac_routing function
>
> was merged in 3.14 and was also put to several stable trees back in
> early 2014. But the commit in stable trees is totally different to
> what is in upstream.
>
> 1) why is it a totally different diff?

The upstream commit was part of a larger reorganization and depended on
lots of earlier changes.  The OXYGEN_PLAY_MUTE* changes are the correct
backport for the old driver; the OXYGEN_PLAY_DACx_SOURCE* changes would
have been meaningless in the old driver.

It was an error to not mention this in the stable commit message.

> 2) do we need the one below, which is marked as "Fixes" the above?
>
> commit 305564413c99514a14a49215790d96b8d71a6295
> Author: Clemens Ladisch <clemens@ladisch.de>
> Date:   Tue Mar 18 09:31:18 2014 +0100
>
>     ALSA: oxygen: Xonar DG(X): fix Stereo Upmixing regression

This reverts exactly those parts that were not backported to -stable,
so it must not (and cannot) be applied to -stable.


Regards,
Clemens

  reply	other threads:[~2015-05-15 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 14:17 ALSA: oxygen stable commit difference Jiri Slaby
2015-05-15 20:40 ` Clemens Ladisch [this message]
2015-05-15 22:18   ` Roman Volkov
2015-05-16  7:17     ` Jiri Slaby

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=555659D6.8090601@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=v1ron@mail.ru \
    /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.