Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp660416pxu; Fri, 11 Dec 2020 11:04:40 -0800 (PST) X-Google-Smtp-Source: ABdhPJw/yPQycUtmgTUvNRBWqCuJePHAQZhM35I8BG1SdbcTFuQaLqWWW1LvKcqPnDdYZnykNQTk X-Received: by 2002:a17:907:20a6:: with SMTP id pw6mr12684832ejb.73.1607713480444; Fri, 11 Dec 2020 11:04:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607713480; cv=none; d=google.com; s=arc-20160816; b=AyOZOKaApdEsx2Zm8OMfoXk/QsjJd3CftjzpJ6S3lUl1mm0yn/ICowvqZRJ3XWqwov t4Kwrd0du2mrpdq/bstdehXXJCNj7LGCy7Je27BSA4vh9ywUWoTSwfeETF2ARbardh0N 5wlwQ3haxbCuYCyei5Xgq9O+pzsthHFuXlXbsmh3maKCoRb2IOSTHqg5R20MmnmvTcXH HvkaoeKDrjsLongWV9ZgEkWuFn36QLvsnnXs/CXv8eH4+BixplVo4JQRkh9tgA2xm2dV I/0PMjWQHvWxDgvlXyvifVspfRqsBlBaaeD9GtJqm/3IyZJQ5ZCfxjEhg4tm5Eo2DL9b bxTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version:date :message-id:subject:references:in-reply-to:cc:to:from; bh=XOECSY5PAWCj0OmpfX3e/ZFVEB5A9/ZNheA3rk2Zx0s=; b=zxrs+kef1fwbL+L0AHRdR4IZ9NJ6IHsZoXHwcSze1vaugzPWgl+Mb3OlI6HlIlhOja JjjxgV8MsG7DIobqwLR9unh16zo0WVjePL930ugLzx7oZN2n7+0Fkk9tsnYOUqqmAaxS f/FEcoP6PBUtq9rBPl1EwCzjwUs1PBM4dlwAvQqDHJ1nl6VD4TvKYQ/zAGNqlJsWJfLN J2mLFQWgBWnnQ0MF96e0Q0AGcsAe/NIbNOFzqcezgW7NJpItn2un0Tyd31fE4GP4soFf mAeDKChxZurr6O5Pk/yqWCIAK28FWeRylPXbB3uBVHFz0rlrUz6X/YUI2OHrTjGDEsmm E31w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s23si5013021ejb.443.2020.12.11.11.04.17; Fri, 11 Dec 2020 11:04:40 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2436507AbgLKRxi (ORCPT + 99 others); Fri, 11 Dec 2020 12:53:38 -0500 Received: from mail.kernel.org ([198.145.29.99]:60798 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2436663AbgLKRwg (ORCPT ); Fri, 11 Dec 2020 12:52:36 -0500 From: Mark Brown Authentication-Results: mail.kernel.org; dkim=permerror (bad message/signature format) To: "H. Nikolaus Schaller" , Rob Herring , linus.walleij@linaro.org Cc: thesven73@gmail.com, devicetree@vger.kernel.org, linux-spi@vger.kernel.org, letux-kernel@openphoenux.org, linux-kernel@vger.kernel.org, Maxime Ripard , linux-gpio@vger.kernel.org, laurent.pinchart@ideasonboard.com, andreas@kemnade.info, kernel@pyra-handheld.com, lukas@wunner.de In-Reply-To: <3bed61807fff6268789e7d411412fbc5cd6ffe2a.1607507863.git.hns@goldelico.com> References: <3bed61807fff6268789e7d411412fbc5cd6ffe2a.1607507863.git.hns@goldelico.com> Subject: Re: [PATCH] spi: dt-bindings: clarify CS behavior for spi-cs-high and gpio descriptors Message-Id: <160770909979.26609.3989372028641790318.b4-ty@kernel.org> Date: Fri, 11 Dec 2020 17:51:39 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 9 Dec 2020 10:57:44 +0100, H. Nikolaus Schaller wrote: > Behavior of CS signal in combination of spi-cs-high and gpio descriptors > is not clearly defined and documented. So clarify the documentation Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: dt-bindings: clarify CS behavior for spi-cs-high and gpio descriptors commit: 2fee9583198eb97b5351feda7bd825e0f778385c 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