summaryrefslogtreecommitdiffstats
path: root/samples/hw_breakpoint
diff options
context:
space:
mode:
authorBartosz Golaszewski <bgolaszewski@baylibre.com>2018-09-21 06:40:14 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-09-28 15:14:54 +0200
commitc7235ee3f4b86a01507a12e96a4875ba9b4be842 (patch)
tree2eef5d2d07b4be90ad768db94ce4753b1c5441b4 /samples/hw_breakpoint
parentbf58e8820c48805394ec9e76339f0c4646050432 (diff)
downloadlinux-stable-c7235ee3f4b86a01507a12e96a4875ba9b4be842.tar.gz
linux-stable-c7235ee3f4b86a01507a12e96a4875ba9b4be842.tar.bz2
linux-stable-c7235ee3f4b86a01507a12e96a4875ba9b4be842.zip
nvmem: remove the global cell list
Nvmem subsystem keeps a global list of cells that, for non-DT systems, can only be referenced by cell name, which makes it impossible to have more than one nvmem device with cells named the same. This patch makes every nvmem device the owner of the list of its cells. This effectively removes the support for non-DT systems, but it will be reintroduced following a different approach in subsequent patches. This isn't a problem as support for board files in nvmem is currently broken anyway: any user that would try to get an nvmem cell from the global cell list would remove the cell after the calling nvmem_cell_put(). This can cause anything from a subsequent user not being able to get the cell to double free errors if more users hold reference to the same cell at the same time. Fortunately there are no such users which allows us to rework this part. Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'samples/hw_breakpoint')
0 files changed, 0 insertions, 0 deletions