public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Paul Menzel <paulepanter@users.sourceforge.net>
Cc: Dave Airlie <airlied@linux.ie>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Alex Deucher <alexdeucher@gmail.com>
Subject: Re: drm fixes for 3.11: Tag more patches for stable?
Date: Fri, 09 Aug 2013 12:40:21 +0200	[thread overview]
Message-ID: <5204C715.70501@vodafone.de> (raw)
In-Reply-To: <1376040290.5808.3.camel@mattotaupa>

Am 09.08.2013 11:25, schrieb Paul Menzel:
> Dear Dave,
>
>
> Am Freitag, den 09.08.2013, 05:53 +0100 schrieb Dave Airlie:
>
> […]
>
>> The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:
>>
>>    Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)
>>
>> are available in the git repository at:
>>
>>    git://people.freedesktop.org/~airlied/linux drm-fixes
>>
>> for you to fetch changes up to e42f5814212079aecd5826dba10588a896ac0862:
>>
>>    Merge tag 'drm-intel-fixes-2013-08-08' of git://people.freedesktop.org/~danvet/drm-intel into drm-fixes (2013-08-09 09:09:37 +1000)
>>
>> ----------------------------------------------------------------
>>
>> Aaron Lu (1):
>>        drm/i915: avoid brightness overflow when doing scale
>>
>> Alex Deucher (11):
>>        drm/radeon: properly handle pm on gpu reset
>>        drm/radeon: select audio dto based on encoder id for DCE3
>>        drm/radeon/dpm: adjust thermal protection requirements
>>        drm/radeon/dpm: fix spread spectrum setup (v2)
>>        drm/radeon/dpm: adjust power state properly for UVD on SI
>>        drm/radeon/dpm: disable sclk ss on rv6xx
>>        drm/radeon: fix audio dto calculation on DCE3+ (v3)
>>        drm/radeon: always program the MC on startup
>>        drm/radeon/cik: use a mutex to properly lock srbm instanced registers
>>        drm/radeon/dpm: require rlc for dpm
>>        drm/radeon: make missing smc ucode non-fatal
>>
>> Christian König (5):
>>        drm/radeon: fix halting UVD
>>        drm/radeon: only save UVD bo when we have open handles
>>        drm/radeon: stop sending invalid UVD destroy msg
>>        drm/radeon: add more UVD CS checking
>>        drm/radeon: remove unnecessary unpin
> as UVD is also in 3.10 should more of these be tagged
> `stable@vger.kernel.org` too? I only checked
>
>          drm/radeon: add more UVD CS checking
>
> and it did not have that tag.

That patch doesn't have the tag because it is a (minor) new feature to 
check the incoming parameters for incorrect values and not a bugfix.

The other three UVD patches are bugfixes and indeed does have the 
necessary tag.

Regards,
Christian.

>
> […]
>
>
> Thanks,
>
> Paul


      parent reply	other threads:[~2013-08-09 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09  4:53 [git pull] drm fixes Dave Airlie
2013-08-09  9:25 ` drm fixes for 3.11: Tag more patches for stable? (was: [git pull] drm fixes) Paul Menzel
2013-08-09 10:33   ` Dave Airlie
2013-08-09 10:40   ` Christian König [this message]

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=5204C715.70501@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=airlied@linux.ie \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulepanter@users.sourceforge.net \
    --cc=torvalds@linux-foundation.org \
    /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