Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Mark Brown <broonie@kernel.org>
To:     Meng.Li@windriver.com, linux-kernel@vger.kernel.org
Cc:     vadivel.muruganx.ramuthevar@linux.intel.com,
        linux-spi@vger.kernel.org, meng.li@windriver.com, vigneshr@ti.com,
        tudor.ambarus@microchip.com
In-Reply-To: <20210311091220.3615-1-Meng.Li@windriver.com>
References: <20210311091220.3615-1-Meng.Li@windriver.com>
Subject: Re: [PATCH] drivers: spi: cadence: set cqspi to the driver_data field of struct device
Message-Id: <161547949200.51229.6800375335632446420.b4-ty@kernel.org>
Date:   Thu, 11 Mar 2021 16:18:12 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 11 Mar 2021 17:12:20 +0800, Meng.Li@windriver.com wrote:
> When initialize cadence qspi controller, it is need to set cqspi
> to the driver_data field of struct device, because it will be
> used in function cqspi_remove/suspend/resume(). Otherwise, there
> will be a crash trace as below when invoking these finctions.
> Call trace:
>  cqspi_suspend+0x14/0x44
>  dpm_run_callback+0x50/0x1c0
>  __device_suspend+0x114/0x514
>  ......
>  el0_svc+0x20/0x30
>  el0_sync_handler+0x1a4/0x1b0
>  el0_sync+0x174/0x180

Applied to

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

Thanks!

[1/1] drivers: spi: cadence: set cqspi to the driver_data field of struct device
      commit: ea94191e584b146878f0b7fd4b767500d7aae870

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