public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: v1ron@mail.ru, Greg KH <gregkh@linuxfoundation.org>
Cc: stable <stable@vger.kernel.org>,
	clemens@ladisch.de, Takashi Iwai <tiwai@suse.de>
Subject: ALSA: oxygen stable commit difference
Date: Fri, 15 May 2015 16:17:57 +0200	[thread overview]
Message-ID: <55560015.9080604@suse.cz> (raw)

[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

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. I am attaching version from upstream and from
3.12 for example.

I have two questions:
1) why is it a totally different diff?
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


thanks,
- -- 
js
suse labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVVgARAAoJEL0lsQQGtHBJjXAQAIACYbsS7GHJs0JxatW+ua6w
MuiNmQqRQk6A5xvQ50mBnrBS7keD2vy7LhLA6yH/czCxwrJbxtEg+HNIEJ9hQ2T3
kMLlkxRXkMn4G3ajQL4x+Ne9FCvzOieYgpn/Jb27vLISyRNJpF9mv069CUk6qA2b
IEaaQjuu9thF9yXw4zFUGzYC1vK2UqHdpl2Bi/rAmEfucLQHFgLFG6LGWfCnxv77
nBxEhds7OARnNhgJ5AW9gvv+fGQ8YoHCAFgxRIDrxzELV75BvlS4YZR/n72qb3s0
pX3EDiId62zkhvtu3H1zTbjRLunqf2rZISzcorcOvZniCsYnFkA2NQFHWCXbxG1Q
7LrRNeLktxYZ0NUjTqpchxJ26Tm1x6iIjHmgRmIdJoh/oL0Vgt4Tfna+jQvsJyOd
fu9YVhLHp9uc+hgR+w3wL1VoiafeK9QlgxQ+m0ztKnp8hpN+TQBoaAEBkmlMG8uu
5/pI7STn2yHmzGZMWqlq6UgDSrFI/AeMD8RnEW24idtY4Aqb3gEIXnZq37LHQ4te
mBJZJl4zr+HDJeznR2wSLs+ZtOUIVtfE1exF4Qqwg66r+aobbZ3wk+mI9njjt0L9
JwXneMXmK0nx6q8Jc6NFM0pRkOW/dE1HGFdw/naeKTACefl+LfR2ldr44+S7y7IZ
isu5x2hPiMwKcFCf6/4e
=S0ql
-----END PGP SIGNATURE-----

[-- Attachment #2: 312.patch --]
[-- Type: application/mbox, Size: 1581 bytes --]

[-- Attachment #3: upstream.patch --]
[-- Type: application/mbox, Size: 3193 bytes --]

             reply	other threads:[~2015-05-15 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 14:17 Jiri Slaby [this message]
2015-05-15 20:40 ` ALSA: oxygen stable commit difference Clemens Ladisch
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=55560015.9080604@suse.cz \
    --to=jslaby@suse.cz \
    --cc=clemens@ladisch.de \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox