Message ID | 20250221165333.2780888-1-raag.jadav@intel.com |
---|---|
Headers | show |
Series | Convert to use devm_kmemdup_array() | expand |
On Fri, Feb 21, 2025 at 10:23:20PM +0530, Raag Jadav wrote: > This series is the second wave of patches to add users of newly introduced > devm_kmemdup_array() helper. Original series on [1]. > > This depends on changes available on immutable tag[2]. Feel free to pick > your subsystem patches with it, or share your preferred way to route them. > > [1] https://lore.kernel.org/r/20250212062513.2254767-1-raag.jadav@intel.com > [2] https://lore.kernel.org/r/Z7cqCaME4LxTTBn6@black.fi.intel.com Update: Anyone wishing to pull from this series, please use the updated tag[3]. I'll wait for a few days for review comments and send out a v2 with fbdev fix. [3] https://lore.kernel.org/r/Z7xGpz3Q4Zj6YHx7@black.fi.intel.com Apologies for the inconvenience. Raag
On Mon, Feb 24, 2025 at 01:46:29PM +0000, Mark Brown wrote: > On Fri, Feb 21, 2025 at 10:23:20PM +0530, Raag Jadav wrote: > > This series is the second wave of patches to add users of newly introduced > > devm_kmemdup_array() helper. Original series on [1]. > > > > This depends on changes available on immutable tag[2]. Feel free to pick > > your subsystem patches with it, or share your preferred way to route them. > > Please don't combine patches for multiple subsystems into a single patch > series, it just makes everything more complex to deal with - it creates > cross tree issues that wouldn't otherwise exist. Sure, will split v2 per subsystem. Raag
On Fri, 21 Feb 2025 22:23:20 +0530, Raag Jadav wrote: > This series is the second wave of patches to add users of newly introduced > devm_kmemdup_array() helper. Original series on [1]. > > This depends on changes available on immutable tag[2]. Feel free to pick > your subsystem patches with it, or share your preferred way to route them. > > [1] https://lore.kernel.org/r/20250212062513.2254767-1-raag.jadav@intel.com > [2] https://lore.kernel.org/r/Z7cqCaME4LxTTBn6@black.fi.intel.com > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [09/13] regulator: devres: use devm_kmemdup_array() commit: 6ddd1159825c516b8f64fda83177c161434141f5 [10/13] regulator: cros-ec: use devm_kmemdup_array() commit: c5c4ce6612bb25ce6d6936d8ade96fcba635da54 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