[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171213092812.26472-1-brgl@bgdev.pl>
Date: Wed, 13 Dec 2017 10:28:09 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Mark Brown <broonie@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, Lars-Peter Clausen <lars@...afoo.de>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Bartosz Golaszewski <brgl@...ev.pl>
Subject: [PATCH 0/3] regmap: follow-up for ("regmap: allow to disable all locking mechanisms")
Hi Mark,
this series is a follow-up for my previous patch. The first commit
renames the empty locking routine introduced in it - I agree with Andy
that it just looks better.
The second patch disables the debugfs entries when locking is disabled
as suggested by Lars-Peter.
The last patch is optional - feel free to drop it if you think it's not
necessary. I just noticed that most frameworks duplicate any name
strings, if it's possible that an unaware user gives us a pointer to
a temporary buffer. While I haven't found any such instance in the
current kernel, I believe it would make regmap safer for the future.
Bartosz Golaszewski (3):
regmap: rename regmap_lock_unlock_empty() to regmap_lock_unlock_none()
regmap: don't create the debugfs entries if locking is disabled
regmap: duplicate the name string stored in regmap
drivers/base/regmap/internal.h | 2 ++
drivers/base/regmap/regmap-debugfs.c | 5 +++++
drivers/base/regmap/regmap.c | 15 ++++++++++++---
3 files changed, 19 insertions(+), 3 deletions(-)
--
2.15.1
Powered by blists - more mailing lists