Messages in this thread | | | From | Nishanth Menon <> | Subject | Re: [PATCH] soc:ti:omap_prm: Use of_device_get_match_data() | Date | Fri, 15 Apr 2022 14:59:05 -0500 |
| |
Hi cgel.zte@gmail.com,
On Mon, 7 Mar 2022 03:37:36 +0000, cgel.zte@gmail.com wrote: > From: Minghao Chi (CGEL ZTE) <chi.minghao@zte.com.cn> > > Use of_device_get_match_data() to simplify the code. > >
I have applied the following to branch ti-drivers-soc-next on [1]. Thank you!
[1/1] soc: ti: omap_prm: Use of_device_get_match_data() commit: cabfa5b46573b4e5ded52b4296a831745c6d32b5
For future reference (I have edited the commit): * Please use to seperate topics in $subject * esp when optimizing, look for potential side effect and explain in commit message that this is fine. (omap_prm_id_table in this case could have been empty and should have been explained in the commit message)
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] git://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
| |