Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751575AbdGZNsO (ORCPT ); Wed, 26 Jul 2017 09:48:14 -0400 Received: from mail-lf0-f67.google.com ([209.85.215.67]:36120 "EHLO mail-lf0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750883AbdGZNsN (ORCPT ); Wed, 26 Jul 2017 09:48:13 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170724133540.32200-1-ricardo.ribalda@gmail.com> <20170724133540.32200-2-ricardo.ribalda@gmail.com> <40ac5a58-9e02-0240-ae87-0b1c9375873b@amd.com> From: Ricardo Ribalda Delgado Date: Wed, 26 Jul 2017 15:47:51 +0200 Message-ID: Subject: Re: [PATCH 01/14] amdgpu: powerplay: Remove unused function To: Harry Wentland Cc: Alex Deucher , =?UTF-8?Q?Christian_K=C3=B6nig?= , David Airlie , Rex Zhu , Tom St Denis , Eric Huang , Huang Rui , Dan Carpenter , "Edward O'Callaghan" , Kees Cook , "Andrew F. Davis" , Hawking Zhang , Baoyou Xie , Masahiro Yamada , Colin Ian King , =?UTF-8?Q?Nils_Wallm=C3=A9nius?= , Joe Perches , amd-gfx@lists.freedesktop.org, "dri-devel@lists.freedesktop.org" , LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1204 Lines: 46 Hi Harry On Mon, Jul 24, 2017 at 5:45 PM, Harry Wentland wrote: > On 2017-07-24 10:06 AM, Ricardo Ribalda Delgado wrote: >> Hi Harry >> On Mon, Jul 24, 2017 at 4:01 PM, Harry Wentland wrote: >> >>> >>> This is used and needed by the DC display driver. See >>> display/amdgpu_dm/amdgpu_dm_services.c:193 in Alex's amd-staging-4.11 tree: >>> >>> https://cgit.freedesktop.org/~agd5f/linux/tree/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_services.c?h=amd-staging-4.11 >>> >> >> I could not find any reference to the function in linux-next (>4.12) >> >> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/drm/amd >> >> Is there any plan to merge Alex's amd-stagin tree? > > The plan is to merge/upstream the amd/display portion of Alex's > amd-staging tree. We're currently working on the community feedback we > received to get it into shape. Is there any timeframe for this? At least we should remove the pr_info("min_core_set_clock not set\n"); message. it is (very) misleading right now. Regards! > > Harry > >> >> Sorry, I am not very familiar with this subsystem. >> >> Regards! >> -- Ricardo Ribalda