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=-14.4 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,USER_AGENT_GIT 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 94140C47078 for ; Fri, 21 May 2021 15:08:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5F64E613CC for ; Fri, 21 May 2021 15:08:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233248AbhEUPJ3 (ORCPT ); Fri, 21 May 2021 11:09:29 -0400 Received: from mail.kernel.org ([198.145.29.99]:49242 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232206AbhEUPJ3 (ORCPT ); Fri, 21 May 2021 11:09:29 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 79947613AF; Fri, 21 May 2021 15:08:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1621609686; bh=7ykpPg7h0iFlH71bVYS2r53l+t1SGzyOmhVqCVEl/ZA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=I34qb25lW8m1aKnm/TsBBTUvPks6ZLbZ6HzqiAGBpvadRDjMO+2Ru6wRQudY7Jcoc VlXiwoj4XT5e+kI2sYA7Ydtf8KV9Sfpis4X0arUxnEXn/+YGPJ9/1C5SiWxeavmVFP nsap1VO13oW9zlZpKdGPsqp4PN2ZolqZyfHiGw+/Mt8Rtv9vF3wJPI6ypWQD3lz98v xDAljXvkkkMlWWwHsAqsHiMxNg/zLmG0bLF69gi1rDQLQ7CK9ZX/c8WYy3I+hcMytU 0H/QtmFFu62tQLaA20SO4ja1lE2nCY+b8aJIXmNHuQgqi72ciGgpXU6GUsXPnCsXhv exN53HMmTqRiw== From: Mark Brown To: Vladimir Oltean , linux-spi@vger.kernel.org Cc: Mark Brown , Guenter Roeck , Vladimir Oltean Subject: Re: [PATCH v1 0/2] Export the spi-sc18is602's max transfer len limit to SPI slave drivers Date: Fri, 21 May 2021 16:07:59 +0100 Message-Id: <162160967729.10785.5397629735840128841.b4-ty@kernel.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20210520131238.2903024-1-olteanv@gmail.com> References: <20210520131238.2903024-1-olteanv@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-spi@vger.kernel.org On Thu, 20 May 2021 16:12:36 +0300, Vladimir Oltean wrote: > These 2 patches make it possible for a SPI device driver which uses > large transfer sizes (256 bytes) to limit itself to the maximum length > supported by the spi-sc18is602 hardware. > > Tested with 200 byte buffers on the SC18IS602B. > > Vladimir Oltean (2): > spi: sc18is602: don't consider the chip select byte in > sc18is602_check_transfer > spi: sc18is602: implement .max_{transfer,message}_size() for the > controller > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/2] spi: sc18is602: don't consider the chip select byte in sc18is602_check_transfer commit: bda7db1d952c3ff7c24c11bc295aa72aaeb98451 [2/2] spi: sc18is602: implement .max_{transfer,message}_size() for the controller commit: b4e46c9954ad55092502e1e8c44ceb9b6744bade 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