Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp479862ybt; Fri, 19 Jun 2020 06:30:51 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwRfbnQqWF0uFghkS4GaCC8HjhYJpa1kVbNiFDeS8urA4yn+rp/h6IesjgJgFm14H/zGUNH X-Received: by 2002:a17:906:b28e:: with SMTP id q14mr3597556ejz.484.1592573451138; Fri, 19 Jun 2020 06:30:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592573451; cv=none; d=google.com; s=arc-20160816; b=ahmUokBrZBzk/CbWCFu0CSaRIKIwtPaLlhBrizuBrjCFyva1bHfAjGNJpW/6wcyHhB OQGsvc+rBRzdoeF+HLyjmW+itc19Qhc2nmozD9QXKoGNFEkIMrMvRQ0k+PTj5KaROYwj C9Gx7XiEDwKFPaxNYzHitiaU+2TCCsRbbPvzNwqhKzkdVVzYJckRdrsuUuzgn/W3S1S7 RHOE5tyg1s2NtuzptLQFQDrH4WtDtM0N6Vecb6XZMHgNBinckcOd5g7e2sFnCLqNfYtr Q/UBjEMEJBw5+F2fZeAxY/zdAQPn8MYCRciGaJv4HlLwYq7JTTCNSFN8CBFNcnTBBmAT QeBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:subject:references:in-reply-to :cc:to:from:date:dkim-signature; bh=s54TIs6SIsYq49iEeEd0DyXcH407bo032SwTu51ORzY=; b=vpEuQr2jds17YRLNW5YCyAXDgFKAodsMLY+ZDeF6C5hIrZ3y0HDqE6UfcYzk0BMlOX oEG/aLz4kD10GpRnhmRm1V5H5KyKHCdeeSrdKZ5MSX8lY4+pb5QxSlfKm84NnoIvLHQs 3EkeSCVIeuehj2uc/JxUmHGIOaw0MHxeQgyBkGCWfE3TGKzRzViyryRpdxFmNHSPqqFk AqncwZ3hbvIXvzi0fviVhEfUwEE7zUysOvJww1aIHYZ2wyhco8ZBdziWxba7u+gEx935 BxcQ9jIZrRTZy7d7UEnZ1fMFhUJT+fRiNyJ0jO2w7SbFNDFjr+dk5SoDHR+K5I/c4yBQ 3qDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=o2GfRR17; 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 mf5si3656944ejb.186.2020.06.19.06.30.28; Fri, 19 Jun 2020 06:30:51 -0700 (PDT) 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; dkim=pass header.i=@kernel.org header.s=default header.b=o2GfRR17; 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 S1731131AbgFSN23 (ORCPT + 99 others); Fri, 19 Jun 2020 09:28:29 -0400 Received: from mail.kernel.org ([198.145.29.99]:46308 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732503AbgFSN2G (ORCPT ); Fri, 19 Jun 2020 09:28:06 -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 2E6F221556; Fri, 19 Jun 2020 13:28:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592573285; bh=PFkCCeYnJboxa0bSQm5EdkilSpndfFBjlZlTuD7GYZI=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=o2GfRR17AIys3dzQSLK9VRQTBfHMgWdkbVioUwKPe8fXgqMOrwCrQUyoFVkNyrsXP xZtDzPvlotCzDGQ+zFwARvX8jOJL7hr9xt4RzQeB4TEx7Aiyg71/e4PY271FExWA1W PGKnMmmfPc7kZQ4TtGfVXJTC4qiaDmpytvuI1564= Date: Fri, 19 Jun 2020 14:28:03 +0100 From: Mark Brown To: Vignesh Raghavendra , Tudor Ambarus Cc: dinguyen@kernel.org, Boris Brezillon , Ramuthevar Vadivel Murugan , linux-spi@vger.kernel.org, simon.k.r.goldschmidt@gmail.com, linux-kernel@vger.kernel.org, marex@denx.de, linux-mtd@lists.infradead.org In-Reply-To: <20200601070444.16923-1-vigneshr@ti.com> References: <20200601070444.16923-1-vigneshr@ti.com> Subject: Re: [RESEND PATCH v3 0/8] mtd: spi-nor: Move cadence-qaudspi to spi-mem framework Message-Id: <159257327822.5984.1131311345326865649.b4-ty@kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 1 Jun 2020 12:34:36 +0530, Vignesh Raghavendra wrote: > This series is a subset of "[PATCH v12 0/4] spi: cadence-quadspi: Add > support for the Cadence QSPI controller" by Ramuthevar,Vadivel MuruganX > that intended to move > cadence-quadspi driver to spi-mem framework > > Those patches were trying to accomplish too many things in a single set > of patches and need to split into smaller patches. This is reduced > version of above series. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/8] mtd: spi-nor: cadence-quadspi: Make driver independent of flash geometry commit: 834b4e8d344139ba64cda22099b2b2ef6c9a542d [2/8] mtd: spi-nor: cadence-quadspi: Provide a way to disable DAC mode commit: a99705079a91e6373122bd0ca2fc129b688fc5b3 [3/8] mtd: spi-nor: cadence-quadspi: Don't initialize rx_dma_complete on failure commit: 48aae57f0f9f57797772bd462b4d64902b1b4ae1 [4/8] mtd: spi-nor: cadence-quadspi: Fix error path on failure to acquire reset lines commit: c61088d1f9932940af780b674f028140eda09a94 [5/8] mtd: spi-nor: cadence-quadspi: Handle probe deferral while requesting DMA channel commit: 935da5e5100f57d843cac4781b21f1c235059aa0 [6/8] mtd: spi-nor: cadence-quadspi: Drop redundant WREN in erase path commit: 41b5ed6e677ca73cb031b7657eefb5cf27071be3 [7/8] mtd: spi-nor: Convert cadence-quadspi to use spi-mem framework commit: a314f6367787ee1d767df9a2120f17e4511144d0 [8/8] spi: Move cadence-quadspi driver to drivers/spi/ commit: 31fb632b5d43ca16713095b3a4fe17e3d7331e28 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