All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Emil Velikov <emil.l.velikov@gmail.com>,
	Arindam Nath <arindam.nath@amd.com>
Cc: ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amdgpu: handle more than 10 UVD sessions (v2)
Date: Tue, 12 Apr 2016 15:26:08 +0200	[thread overview]
Message-ID: <570CF770.6090103@vodafone.de> (raw)
In-Reply-To: <CACvgo50ckMQVjz+0HhpOu=rS3DBr+EkFNaCVJCisAr3Au=1WCQ@mail.gmail.com>

Am 12.04.2016 um 15:14 schrieb Emil Velikov:
> On 12 April 2016 at 12:46, Christian König <deathsimple@vodafone.de> wrote:
>> From: Arindam Nath <arindam.nath@amd.com>
>>
>> Change History
>> --------------
>>
>> v2:
>> - Make firmware version check correctly. Firmware
>>    versions >= 1.80 should all support 40 UVD
>>    instances.
> Fwiw, this is the type of information that people [unfamiliar with the
> firmware] will appreciate in the commit message. Currently it's almost
> like a "here a magic commit"
>
> Can we have something like that for the future, pretty please ?

Well, unfortunately not most of the time. A lot of firmware changes are 
usually about top secrete stuff where you need explicit approval.

Getting this for each individual firmware change is usually just to much 
overhead.

Christan.

>
> -Emil

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-04-12 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 11:46 [PATCH] drm/amdgpu: handle more than 10 UVD sessions (v2) Christian König
2016-04-12 13:14 ` Emil Velikov
2016-04-12 13:26   ` Christian König [this message]
2016-04-12 15:22 ` Alex Deucher

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=570CF770.6090103@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=arindam.nath@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.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.