From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 15A94C4360C for ; Tue, 8 Oct 2019 15:18:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DE03E2070B for ; Tue, 8 Oct 2019 15:18:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570547882; bh=pu15L9RwUEae6WQjWmvYaOl1fDYuNLf8hrqu5nJEfk0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=thqWiYyevHm4DyvebAk6TbLWi2Ypvl9CpWS/nF0U96EptT6WoAx/+Khz5wBEjSrDQ 3WoswKPncY/DQcAjkaZgbOWWu+rQuV7r12pUybwFXBceGRqnBCKhh2XqhktH4WfsyN t2z2Sz7fhm+swtxSQnA8rRtILyndh9HTB6ElJHRg= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728054AbfJHPSC (ORCPT ); Tue, 8 Oct 2019 11:18:02 -0400 Received: from mail.kernel.org ([198.145.29.99]:41156 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725839AbfJHPSB (ORCPT ); Tue, 8 Oct 2019 11:18:01 -0400 Received: from localhost (unknown [89.205.136.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8A90B206C0; Tue, 8 Oct 2019 15:18:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570547881; bh=pu15L9RwUEae6WQjWmvYaOl1fDYuNLf8hrqu5nJEfk0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=nbDY0sw3u8LA9uVR+RmMolTPUQLU5DB8aI9i9TF3dGYpFQhqnUeT/54uJWyK/mNqO kz0nOuGyL9sDpstiPmnATSUxHBffFQVE5OjbVpMSBT2TJ04F1YSwPhkJ/cmwU9DkgB tW+/Za3J9e5uxhxKvWPyqfl23hR+7nPyjbnBzU0Q= Date: Tue, 8 Oct 2019 17:17:57 +0200 From: Greg Kroah-Hartman To: Pavel Machek Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, Charlene Liu , Dmytro Laktyushkin , Bhawanpreet Lakha , Alex Deucher , Sasha Levin Subject: Re: [PATCH 4.19 033/106] drm/amd/display: support spdif Message-ID: <20191008151757.GB2872679@kroah.com> References: <20191006171124.641144086@linuxfoundation.org> <20191006171140.114447492@linuxfoundation.org> <20191008133741.GG608@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191008133741.GG608@amd> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 08, 2019 at 03:37:41PM +0200, Pavel Machek wrote: > Hi! > > > [ Upstream commit b5a41620bb88efb9fb31a4fa5e652e3d5bead7d4 ] > > > > [Description] > > port spdif fix to staging: > > spdif hardwired to afmt inst 1. > > spdif func pointer > > spdif resource allocation (reserve last audio endpoint for spdif only) > > I'm sorry, but I don't understand this changelog. Code below modifies > whitespace, adds a debug output, and uses local variable for > pool->audio_count. > > Does not seem to be a bugfix, and does not seem to do anything with > staging. That's what the original changelog had in it, so I kept it. thanks, greg k-h