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=-9.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 1D784C433E1 for ; Tue, 18 Aug 2020 17:40:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D6FE02078B for ; Tue, 18 Aug 2020 17:40:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1597772409; bh=vhi5iImj5rpc1HCF6tflR5/gmVfFRnZe0Q1H8J1CIQU=; h=Date:From:To:Cc:In-Reply-To:References:Subject:List-ID:From; b=hCI2tD8LF5GcK7DMZjYDVKP0K0dCrEkNPCmQHCVGHVDTCzB9J6/gR+Nj3Mk9cA+WK Eo/BjMBJVBSlW8HqTRPkAF6xpf2hChVa+UTpW2fT17h9l+trlvbviY69xAJ65JKjFT 25uYdFHFzXyCnye/toIabIcEJdNnxhnKWZoqgTb4= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726946AbgHRRkH (ORCPT ); Tue, 18 Aug 2020 13:40:07 -0400 Received: from mail.kernel.org ([198.145.29.99]:58404 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726716AbgHRRkD (ORCPT ); Tue, 18 Aug 2020 13:40:03 -0400 Received: from localhost (fw-tnat.cambridge.arm.com [217.140.96.140]) (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 5B01B20674; Tue, 18 Aug 2020 17:40:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1597772402; bh=vhi5iImj5rpc1HCF6tflR5/gmVfFRnZe0Q1H8J1CIQU=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=W0/tCenkdLxWuq9DuP4pl5WQcneKduqX5eyQEDgaOCxoz2k6PoOjjku4t9ap0FZ1Z wnmqFwEuJ2KJKV3b1BLNA+ZrNPMZEawNR3TQo392nmQ0iDEhCot7Ltbfon5AAV5B8t oIL4zXmPmcaoqD1XW3bn9zNoc3qxPNGBMnLPTBHg= Date: Tue, 18 Aug 2020 18:39:32 +0100 From: Mark Brown To: heiko@sntech.de, Johan Jonker Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org, lgirdwood@gmail.com, devicetree@vger.kernel.org, sugar.zhang@rock-chips.com, linux-arm-kernel@lists.infradead.org, alsa-devel@alsa-project.org, linux-rockchip@lists.infradead.org In-Reply-To: <20200815112437.6662-1-jbx6244@gmail.com> References: <20200815112437.6662-1-jbx6244@gmail.com> Subject: Re: [RFC PATCH v1 1/2] ASoC: rockchip-spdif: add description for rk3308 Message-Id: <159777235702.24785.6071406092979338870.b4-ty@kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 15 Aug 2020 13:24:36 +0200, Johan Jonker wrote: > A test with the command below shows that the compatible string > > "rockchip,rk3308-spdif", "rockchip,rk3328-spdif" > > is already in use, but is not added to a document. > The current fallback string "rockchip,rk3328-spdif" points to a data > set enum RK_SPDIF_RK3366 in rockchip_spdif.c that is not used both > in the mainline as in the manufacturer kernel. > (Of the enum only RK_SPDIF_RK3288 is used.) > So if the properties don't change we might as well use the first SoC > in line as fallback string and add the description for rk3308 as: > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: rockchip-spdif: add description for rk3308 commit: a8535ae7034e3547f4f7a8c7ca03a6ee72097fb0 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark