Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Mark Brown <broonie@kernel.org>
To:     sfr@canb.auug.org.au, skhan@linuxfoundation.org,
        siddhpant.gh@gmail.com
Cc:     linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <4e6187a4-d0f8-4750-e407-e09cc1c91789@gmail.com>
References: <4e6187a4-d0f8-4750-e407-e09cc1c91789@gmail.com>
Subject: Re: [PATCH] spi: Doc fix - Describe add_lock and dma_map_dev in spi_controller
Message-Id: <165237312070.1053498.16178641624638760904.b4-ty@kernel.org>
Date:   Thu, 12 May 2022 17:32:00 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 12 May 2022 20:06:45 +0530, Siddh Raman Pant wrote:
> This fixes the corresponding warnings during building the docs.
> 
> 

Applied to

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

Thanks!

[1/1] spi: Doc fix - Describe add_lock and dma_map_dev in spi_controller
      commit: 75d6fe48a21a0ea1565228c12b9c16f3fb37b673

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