Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     Linus Walleij <linus.walleij@linaro.org>,
        =?utf-8?q?M=C3=A5rten_Lindahl?= <marten.lindahl@axis.com>
Cc:     linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
        linux-kernel@vger.kernel.org, kernel@axis.com
In-Reply-To: <20230602-pl022-defer-fix-v2-1-383f6bc2293a@axis.com>
References: <20230602-pl022-defer-fix-v2-1-383f6bc2293a@axis.com>
Subject: Re: [PATCH v2] spi: spl022: Probe defer is no error
Message-Id: <168597693914.38297.2144180817294753536.b4-ty@kernel.org>
Date:   Mon, 05 Jun 2023 15:55:39 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 02 Jun 2023 20:12:54 +0200, Mårten Lindahl wrote:
> When the spi controller is registered and the cs_gpiods cannot be
> assigned, causing a defer of the probe, there is an error print saying:
> "probe - problem registering spi master"
> 
> This should not be announced as an error. Print this message for all
> errors except for the probe defer.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: spl022: Probe defer is no error
      commit: 8098a931c080d32687aee72a1dfac98507a6034b

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