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:     linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        devicetree@vger.kernel.org, linux-spi@vger.kernel.org,
        Kuldeep Singh <singh.kuldeep87k@gmail.com>
Cc:     Linus Walleij <linus.walleij@linaro.org>,
        Rob Herring <robh+dt@kernel.org>
In-Reply-To: <20220309171847.5345-1-singh.kuldeep87k@gmail.com>
References: <20220309171847.5345-1-singh.kuldeep87k@gmail.com>
Subject: Re: [PATCH v3] spi: Update clock-names property for arm pl022
Message-Id: <164703017513.264521.4229870520812086440.b4-ty@kernel.org>
Date:   Fri, 11 Mar 2022 20:22:55 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 9 Mar 2022 22:48:47 +0530, Kuldeep Singh wrote:
> PL022 has two input clocks named sspclk and apb_pclk. Current schema
> refers to two notations of sspclk which are indeed same and thus one can
> be dropped. Update clock-names property to reflect the same.
> 
> 

Applied to

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

Thanks!

[1/1] spi: Update clock-names property for arm pl022
      commit: 1889421a891ff439b25495011b8b75f81660abca

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