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:     sanju.mehta@amd.com, Shreeya Patel <shreeya.patel@collabora.com>
Cc:     Lucas Tanure <tanureal@opensource.cirrus.com>,
        krisman@collabora.com, alvaro.soliverez@collabora.com,
        linux-kernel@vger.kernel.org, kernel@collabora.com,
        linux-spi@vger.kernel.org
In-Reply-To: <20220819123630.368462-1-shreeya.patel@collabora.com>
References: <20220819123630.368462-1-shreeya.patel@collabora.com>
Subject: Re: [PATCH v2] spi: amd: Configure device speed
Message-Id: <166194966658.85432.16168252045246459215.b4-ty@kernel.org>
Date:   Wed, 31 Aug 2022 13:41:06 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 19 Aug 2022 18:06:30 +0530, Shreeya Patel wrote:
> From: Lucas Tanure <tanureal@opensource.cirrus.com>
> 
> Number of clock frequencies are supported by AMD controller
> which are mentioned in the amd_spi_freq structure table.
> 
> Create mechanism to configure device clock frequency such
> that it is strictly less than the requested frequency.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: amd: Configure device speed
      commit: 3fe26121dc3a9bf64e18fe0075cd9a92c9cd1b1a

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