[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <366447c1-003c-71fe-98e4-ce66890e17ea@daenzer.net>
Date: Thu, 11 May 2017 11:40:15 +0900
From: Michel Dänzer <michel@...nzer.net>
To: Christian König <christian.koenig@....com>,
SF Markus Elfring <elfring@...rs.sourceforge.net>,
Alex Deucher <alexander.deucher@....com>,
David Airlie <airlied@...ux.ie>
Cc: kernel-janitors@...r.kernel.org, dri-devel@...ts.freedesktop.org,
amd-gfx@...ts.freedesktop.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] GPU-DRM-Radeon: Fine-tuning for three function
implementations
On 10/05/17 08:30 PM, Christian König wrote:
> Am 10.05.2017 um 02:23 schrieb Michel Dänzer:
>> On 03/05/17 09:46 PM, Christian König wrote:
>>> Am 02.05.2017 um 22:04 schrieb SF Markus Elfring:
>>>> From: Markus Elfring <elfring@...rs.sourceforge.net>
>>>> Date: Tue, 2 May 2017 22:00:02 +0200
>>>>
>>>> Three update suggestions were taken into account
>>>> from static source code analysis.
>>>>
>>>> Markus Elfring (3):
>>>> Use seq_putc() in radeon_sa_bo_dump_debug_info()
>>>> Use seq_puts() in radeon_debugfs_pm_info()
>>>> Use seq_puts() in r100_debugfs_cp_csq_fifo()
>>> Reviewed-by: Christian König <christian.koenig@....com>
>> Based on
>> https://lists.freedesktop.org/archives/dri-devel/2017-May/140837.html
>> and followups, I'm afraid we'll have to make sure Markus' patches have
>> been tested adequately before applying them.
>
> I can't judge the background of that decision, but at least those tree
> patches for radeon looked trivial to me.
Which is part of the issue, see also
https://lists.freedesktop.org/archives/dri-devel/2017-May/140694.html
and other posts in that thread.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
Powered by blists - more mailing lists