Message ID | 20230809100428.2669817-1-chenjiahao16@huawei.com (mailing list archive) |
---|---|
Headers | show |
Series | regulator: Remove redundant of_match_ptr() macros | expand |
On Wed, 09 Aug 2023 10:04:21 +0000, Chen Jiahao wrote: > Since these drivers depend on CONFIG_OF, it makes > no difference to wrap of_match_ptr() here, nor can > we save .text space from it. > > Remove of_match_ptr() macros to clean it up. > > Chen Jiahao (7): > regulator: da9121-regulator: Remove redundant of_match_ptr() macros > regulator: lp87565: Remove redundant of_match_ptr() macros > regulator: hi6421: Remove redundant of_match_ptr() macros > regulator: mcp16502: Remove redundant of_match_ptr() macros > regulator: mpq7920: Remove redundant of_match_ptr() macro > regulator: pfuze100-regulator: Remove redundant of_match_ptr() macro > regulator: tps6286x-regulator: Remove redundant of_match_ptr() macros > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/7] regulator: da9121-regulator: Remove redundant of_match_ptr() macros commit: 3a6d93eb5f27f313ce0f3fa3fb171cd0732c4878 [2/7] regulator: lp87565: Remove redundant of_match_ptr() macros commit: f410cfe8be5788cf09a3f32ce39946c339297821 [3/7] regulator: hi6421: Remove redundant of_match_ptr() macros commit: 656ed7467623674e6cc794a5b2ef79e8b8b81c3f [4/7] regulator: mcp16502: Remove redundant of_match_ptr() macros commit: 3988795eb08c4239e865c4c21a3d5fd6fb2bd055 [5/7] regulator: mpq7920: Remove redundant of_match_ptr() macro commit: c329adf3026034c84ddd61c0b19db53d40510ae7 [6/7] regulator: pfuze100-regulator: Remove redundant of_match_ptr() macro commit: 9e8925eb7fd6e5d93d9dfa9ca4628e897f0db8f1 [7/7] regulator: tps6286x-regulator: Remove redundant of_match_ptr() macros commit: 252b9116aff4d04176adc931cd11f02169df54f1 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