diff options
| author | Calvin Owens <calvin@wbinvd.org> | 2026-07-06 10:19:07 -0700 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2026-07-22 21:14:16 -0700 |
| commit | c693b9eb71232d8abd019789156e38396a08fd8e (patch) | |
| tree | bc1d25b7202c035c57a8ea08f68b933b97b5d922 /fs | |
| parent | 0afc582999b92d942a1b046b107482958607e07e (diff) | |
| download | linux-next-c693b9eb71232d8abd019789156e38396a08fd8e.tar.gz linux-next-c693b9eb71232d8abd019789156e38396a08fd8e.zip | |
pps-gpio: remove dead capture_clear code
The capture_clear field is never set, and all code conditional on it being
set has been unreachable since the platform data logic was removed from
pps-gpio in ee89646619ba ("pps: clients: gpio: Get rid of legacy platform
data").
I think the only logical thing to do here is to remove it all, since no
in-tree code ever actually used it in the first place, and it has been
completely dead code for over five years (since v5.13).
Sashiko asked some questions about the gpiod_get_value() call which caused
me to look deeper and figure this out, but it did not actually notice
capture_clear is never set.
Link: https://lore.kernel.org/f70196bafcf75d9782dd36ed784e42345b6e8a1b.1783355507.git.calvin@wbinvd.org
Fixes: ee89646619ba ("pps: clients: gpio: Get rid of legacy platform data")
Signed-off-by: Calvin Owens <calvin@wbinvd.org>
Closes: https://sashiko.dev/#/patchset/cover.1779733602.git.calvin%40wbinvd.org?part=1
Acked-by: Rodolfo Giometti <giometti@enneenne.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions