[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <169747469034.3008686.12890473266248786472.b4-ty@ti.com>
Date: Mon, 16 Oct 2023 11:45:13 -0500
From: Nishanth Menon <nm@...com>
To: Santosh Shilimkar <ssantosh@...nel.org>,
Rob Herring <robh@...nel.org>
CC: Nishanth Menon <nm@...com>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] soc: ti: knav_qmss_queue: Use device_get_match_data()
Hi Rob Herring,
On Mon, 09 Oct 2023 16:13:43 -0500, Rob Herring wrote:
> Use preferred device_get_match_data() instead of of_match_device() to
> get the driver match data. With this, adjust the includes to explicitly
> include the correct headers.
>
>
I have applied the following to branch ti-drivers-soc-next on [1].
Thank you!
[1/1] soc: ti: knav_qmss_queue: Use device_get_match_data()
commit: 50c01a942b287451ed7bec290ac09e07b91c6253
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists