diff options
author | Koen Vandeputte <koen.vandeputte@ncentric.com> | 2019-01-28 13:54:02 +0100 |
---|---|---|
committer | Koen Vandeputte <koen.vandeputte@ncentric.com> | 2019-01-28 18:17:32 +0100 |
commit | 880a4b334ebc0fc7668343e7feafffa6767d6b08 (patch) | |
tree | f77afc2040557da6ee0df9670c33486d848ee77b /target/linux/gemini | |
parent | c6bebe1a9496f9888e451a7f8aea6db916c0bdf2 (diff) | |
download | upstream-880a4b334ebc0fc7668343e7feafffa6767d6b08.tar.gz upstream-880a4b334ebc0fc7668343e7feafffa6767d6b08.tar.bz2 upstream-880a4b334ebc0fc7668343e7feafffa6767d6b08.zip |
cns3xxx: don't use invalid mask value for clock events
According to a commit from kernel 4.18-rc3, it's not valid
to use "cpu_mask_all" for clock events and it should be
replaced in favor of "cpu_possible_mask" [1]
This warning was seen when booting kernel 4.19 on a cns3xxx board.
Let's fix it also here just to be safe.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.19.18&id=fbfa9260085b5b578a049a90135e5c51928c5f7f
Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
Diffstat (limited to 'target/linux/gemini')
0 files changed, 0 insertions, 0 deletions