summaryrefslogtreecommitdiffstats
path: root/fs/gfs2/recovery.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2020-11-19 19:55:54 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2020-11-19 19:55:54 +0100
commitd748287a28de8955e1756a454e81ab1a73d45ecf (patch)
tree2e49d50315fd330e048429ac036ce23abce92f3e /fs/gfs2/recovery.c
parentMerge tag 'thermal-v5.10-rc5' of git://git.kernel.org/pub/scm/linux/kernel/gi... (diff)
parentregulator: ti-abb: Fix array out of bound read access on the first transition (diff)
downloadlinux-d748287a28de8955e1756a454e81ab1a73d45ecf.tar.xz
linux-d748287a28de8955e1756a454e81ab1a73d45ecf.zip
Merge tag 'regulator-fix-v5.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator
Pull regulator fixes from Mark Brown: "Mostly core fixes here, one set from Michał Mirosław which cleans up some issues introduced as part of the coupled regulators work, one memory leak during probe and two due to regulators which have an input supply name and regulator name which are identical, which is very unusual. There's also a fix for our handling of the similarly unusual case where we can't determine if a regulator is enabled during boot" * tag 'regulator-fix-v5.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator: regulator: ti-abb: Fix array out of bound read access on the first transition regulator: workaround self-referent regulators regulator: avoid resolve_supply() infinite recursion regulator: fix memory leak with repeated set_machine_constraints() regulator: pfuze100: limit pfuze-support-disable-sw to pfuze{100,200} regulator: core: don't disable regulator if is_enabled return error.
Diffstat (limited to 'fs/gfs2/recovery.c')
0 files changed, 0 insertions, 0 deletions