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=-11.0 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=ham 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 C9CADC64E75 for ; Wed, 25 Nov 2020 13:59:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 61E622067D for ; Wed, 25 Nov 2020 13:59:07 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="aQ6aa79R" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729771AbgKYN64 (ORCPT ); Wed, 25 Nov 2020 08:58:56 -0500 Received: from mail.kernel.org ([198.145.29.99]:34718 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725985AbgKYN6z (ORCPT ); Wed, 25 Nov 2020 08:58:55 -0500 Received: from localhost (cpc102334-sgyl38-2-0-cust884.18-2.cable.virginm.net [92.233.91.117]) (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 A4243206F9; Wed, 25 Nov 2020 13:58:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1606312735; bh=o7d9fgU6mXGwYGbLFIRYfmgfnb1HDJ7zjumgwpqARWY=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=aQ6aa79R8DU5b7+nisqI1fjMhRLxU0cT2zvnWXEnMs6Omaq1SeGuiZ/lt6L0LUM9Z dhRKwvyj/K37RZkarmhvHFa+PeFLZJXyiJeJfiOro1W+P6ZJAQTQOCbMvJAfPhlimn R8pdUWCXWhdFJ3eURsdXRVo6haUvVR1T22fbCYfI= Date: Wed, 25 Nov 2020 13:58:30 +0000 From: Mark Brown To: Serge Semin , Lars Povlsen , linux-spi@vger.kernel.org Cc: linux-kernel@vger.kernel.org In-Reply-To: <20201120213414.339701-1-lars.povlsen@microchip.com> References: <20201120213414.339701-1-lars.povlsen@microchip.com> Subject: Re: [PATCH] spi: dw: Fix spi registration for controllers overriding CS Message-Id: <160631270511.29611.7697782706321282080.b4-ty@kernel.org> 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 Fri, 20 Nov 2020 22:34:14 +0100, Lars Povlsen wrote: > When SPI DW memory ops support was introduced, there was a check for > excluding controllers which supplied their own CS function. Even so, > the mem_ops pointer is *always* presented to the SPI core. > > This causes the SPI core sanity check in spi_controller_check_ops() to > refuse registration, since a mem_ops pointer is being supplied without > an exec_op member function. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: dw: Fix spi registration for controllers overriding CS commit: 0abdb0fba07322ce960d32a92a64847b3009b2e2 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