Received-SPF: pass (google.com: domain of linux-kernel+bounces-169222-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: Mark Brown <broonie@kernel.org>
To: =?utf-8?q?Uwe_Kleine-K=C3=B6nig?= <u.kleine-koenig@pengutronix.de>, 
 linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@linux.intel.com>
In-Reply-To: <20240502171518.2792895-1-andriy.shevchenko@linux.intel.com>
References: <20240502171518.2792895-1-andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v1 1/1] spi: bitbang: Add missing MODULE_DESCRIPTION()
Message-Id: <171495749604.1941246.483886233584970643.b4-ty@kernel.org>
Date: Mon, 06 May 2024 10:04:56 +0900
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Thu, 02 May 2024 20:15:18 +0300, Andy Shevchenko wrote:
> The modpost script is not happy
> 
>   WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/spi/spi-bitbang.o
> 
> because there is a missing module description.
> 
> Add it to the module.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: bitbang: Add missing MODULE_DESCRIPTION()
      commit: 8ee46db14169fe1b028078767fda904d2fcbc04e

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