summaryrefslogtreecommitdiff
path: root/net/lapb/Makefile
diff options
context:
space:
mode:
authorWei Yongjun <weiyongjun1@huawei.com>2017-02-14 14:19:32 +0000
committerDavid S. Miller <davem@davemloft.net>2017-02-14 15:02:17 -0500
commit6f2e3f7d9785dacb358b48b44950182b5c13e4bc (patch)
treedbed4d1cfd5590a7d615f129b28caac6632a0de5 /net/lapb/Makefile
parent044950cc48ced25ccb2f4ea7c31228399e19d5d6 (diff)
net_sched: nla_memdup_cookie() can be static
Fixes the following sparse warning: net/sched/act_api.c:532:5: warning: symbol 'nla_memdup_cookie' was not declared. Should it be static? Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/lapb/Makefile')
0 files changed, 0 insertions, 0 deletions
prepared prior to the merge window, but we waited for 4.10-rc1 to have a stable merge base after all the prerequisites were merged. Quoting Jan on the overall changes in these patches: "So I'd like all these 6 patches to go for rc2. The first three patches fix invalidation of exceptional DAX entries (a bug which is there for a long time) - without these patches data loss can occur on power failure even though user called fsync(2). The other three patches change locking of DAX faults so that ->iomap_begin() is called in a more relaxed locking context and we are safe to start a transaction there for ext4" These have received a build success notification from the kbuild robot, and pass the latest libnvdimm unit tests. There have not been any -next releases since -rc1, so they have not appeared there" * 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm: ext4: Simplify DAX fault path dax: Call ->iomap_begin without entry lock during dax fault dax: Finish fault completely when loading holes dax: Avoid page invalidation races and unnecessary radix tree traversals mm: Invalidate DAX radix tree entries only if appropriate ext2: Return BH_New buffers for zeroed blocks
Diffstat (limited to 'net/6lowpan/Makefile')