summaryrefslogtreecommitdiff
path: root/include/trace
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2016-11-30 17:04:52 +0100
committerLuca Coelho <luciano.coelho@intel.com>2017-02-03 16:26:42 +0200
commitcba84570a0eb8826bcd69627fd975935bdcf7eaf (patch)
treef58617a0dc8341ca4a933aeb5f6062cd0594459b /include/trace
parent4b70f07686d75d1eb5d956812cc810944e0b29b2 (diff)
iwlwifi: mvm: fix D3 replay counter value
This fixes a long-standing bug that was introduced when this code was introduced: cfg80211 passes a pointer, but we treat it as if it was passing a value. The result is that we pass the pointer to the firmware, instead of the value. It's not clear how this could ever have worked, unless the firmware is ignoring this value. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Diffstat (limited to 'include/trace')
0 files changed, 0 insertions, 0 deletions
ashes. This can be partly attributed to the fact that ioremap_page_range is lower-level, with fewer protections, as compared to the other functions that an external module would typically call. Those include: ioremap_cache ioremap_nocache ioremap_prot ioremap_uc ioremap_wc ioremap_wt ...each of which wraps __ioremap_caller, which in turn provides a safer way to achieve the mapping. Therefore, stop EXPORT-ing ioremap_page_range. Link: http://lkml.kernel.org/r/1485173220-29010-1-git-send-email-zhongjiang@huawei.com Signed-off-by: zhong jiang <zhongjiang@huawei.com> Reviewed-by: John Hubbard <jhubbard@nvidia.com> Suggested-by: John Hubbard <jhubbard@nvidia.com> Acked-by: Michal Hocko <mhocko@suse.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools/perf/tests/llvm.h')