Received-SPF: pass (google.com: domain of linux-kernel+bounces-169221-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: <20240502154825.2752464-1-andriy.shevchenko@linux.intel.com>
References: <20240502154825.2752464-1-andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v1 1/1] spi: bitbang: Use NSEC_PER_*SEC rather than
 hard coding
Message-Id: <171495749464.1941246.13700108191121303721.b4-ty@kernel.org>
Date: Mon, 06 May 2024 10:04:54 +0900
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Thu, 02 May 2024 18:48:25 +0300, Andy Shevchenko wrote:
> Use NSEC_PER_*SEC rather than the hard coded value of 1000s.
> 
> 

Applied to

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

Thanks!

[1/1] spi: bitbang: Use NSEC_PER_*SEC rather than hard coding
      commit: 645094b41157cce4ec41dc31298646c82f6998e0

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