summaryrefslogtreecommitdiff
path: root/include/crypto/aes.h
diff options
context:
space:
mode:
authorArend Van Spriel <arend.vanspriel@broadcom.com>2017-01-27 12:27:47 +0000
committerKalle Valo <kvalo@codeaurora.org>2017-01-31 09:24:59 +0200
commit0b57010fc18e12c19d14379cd739d4eb7c3898f3 (patch)
tree14c3dc4cfa9ff440d709bfa8617f6779a4a31a92 /include/crypto/aes.h
parentd29afe91af5995306d940b3dfee2419e0bb24a51 (diff)
brcmfmac: allow wowlan support to be per device
The wowlan support is (partially) determined dynamic by checking the device/firmware capabilities. So they can differ per device. So it is not possible to use a static global. Instead use the global as a template and use kmemdup(). When kmemdup() fails the template is used unmodified. Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com> Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com> Reviewed-by: Franky Lin <franky.lin@broadcom.com> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'include/crypto/aes.h')
0 files changed, 0 insertions, 0 deletions
user process. The MEM errors form userspace will result in a SIGKILL and also cause the offending pages to be claimed so they are no longer used in future tasks. SIGKILL is used to ensure that the process does not try to coredump and result in an attempt to read the memory again from within kernel space. Although there is a HV call to scrub the memory (mem_scrub), there is no easy way to guarantee that the real memory address(es) are not used by other tasks. Clearing the error with mem_scrub would zero the memory and cause the other processes to proceed with bad data. The handling of other non-resumable errors remain unchanged and will cause a panic. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/dt-bindings/leds/common.h')