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:     david@protonic.nl
Cc:     linux-kernel@vger.kernel.org, sfr@canb.auug.org.au,
        andy.shevchenko@gmail.com, linux-next@vger.kernel.org,
        linux-spi@vger.kernel.org
In-Reply-To: <20220608153309.2899565-1-david@protonic.nl>
References: <20220608153309.2899565-1-david@protonic.nl>
Subject: Re: [PATCH v2] spi: <linux/spi/spi.h>: Add missing documentation for struct members
Message-Id: <165472119981.3018494.3607522399467236617.b4-ty@kernel.org>
Date:   Wed, 08 Jun 2022 21:46:39 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 8 Jun 2022 17:33:09 +0200, David Jander wrote:
> Fixes these "make htmldocs" warnings:
> 
> include/linux/spi/spi.h:82: warning: Function parameter or member 'syncp' not described in 'spi_statistics'
> include/linux/spi/spi.h:213: warning: Function parameter or member 'pcpu_statistics' not described in 'spi_device'
> include/linux/spi/spi.h:676: warning: Function parameter or member 'pcpu_statistics' not described in 'spi_controller'
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: <linux/spi/spi.h>: Add missing documentation for struct members
      commit: 5dfac65b621733e69b789150a0a3f1bf2f9095a3

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