The patch regmap: debugfs: use memcpy instead of snprintf
has been applied to the regmap tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git 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 >From 20991cdb26ffc51030223320a6dd266f4fc28fbd Mon Sep 17 00:00:00 2001 From: Rasmus Villemoes <[email protected]> Date: Wed, 30 Sep 2015 20:30:26 +0200 Subject: [PATCH] regmap: debugfs: use memcpy instead of snprintf Since we know the length of entry and that there's room enough in the output buffer, using memcpy instead of snprintf is simpler and cheaper. Signed-off-by: Rasmus Villemoes <[email protected]> Signed-off-by: Mark Brown <[email protected]> --- drivers/base/regmap/regmap-debugfs.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/base/regmap/regmap-debugfs.c b/drivers/base/regmap/regmap-debugfs.c index 1ffc101..69894bb 100644 --- a/drivers/base/regmap/regmap-debugfs.c +++ b/drivers/base/regmap/regmap-debugfs.c @@ -370,8 +370,7 @@ static ssize_t regmap_reg_ranges_read_file(struct file *file, if (p >= *ppos) { if (buf_pos + 1 + entry_len > count) break; - snprintf(buf + buf_pos, count - buf_pos, - "%s", entry); + memcpy(buf + buf_pos, entry, entry_len); buf_pos += entry_len; buf[buf_pos] = '\n'; buf_pos++; -- 2.5.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
