summaryrefslogtreecommitdiff
path: root/drivers/usb/gadget/function/f_hid.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2017-02-10 15:52:27 -0500
committerDavid S. Miller <davem@davemloft.net>2017-02-10 15:52:27 -0500
commite40d5d78df539c0c9b6625cdf5b1bc4b14c4d8bf (patch)
treee92dbfbbc3b48bf496d10002c3f5b39b05a86bf5 /drivers/usb/gadget/function/f_hid.c
parent4f2bd6b35b345523ac99b14ce9a1f4a98f21ebdb (diff)
parent63461a028f761f8e45d22d06fb7e7468def024b7 (diff)
Merge branch 'netronome-NFP4000-and-NFP6000-PF-driver'
Jakub Kicinski says: ==================== Netronome NFP4000 and NFP6000 PF driver This is a base PF driver for Netronome NFP4000 and NFP6000 chips. This series doesn't add any exciting new features, it provides a foundation for supporting more advanced firmware applications. Patch 1 moves a bitfield-related helper from our BPF code to the global header. Patch 2 renames the kernel module and adds a new main file. We were considering 3-module approach (pf, vf, common netdev library) but ultimately settled on a single module to keep things simple. Patch 3 adds support for accessing chip internals. It provides a way of configuring access windows to different parts of chip memory and issuing pretty much any commands on chip's NoC. Patches 4, 5, 6, 7, 8 provide support for accessing and interpreting various hardware and firmware information structures. Patch 9 introduces service processor (NSP) ABI. This ABI gives us access to PHY/SFP module configuration and information as well as methods for unloading and loading application firmware. Patches 10 and 11 modify the existing netdev code to make it possible to support multi-port devices (sharing a PCI device). Patch 12 adds a new driver probe path which will be used for the PF PCI device IDs. It utilizes the newly added infrastructure and is able to load application FW and spawn netdevs for all card's ports. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/usb/gadget/function/f_hid.c')
0 files changed, 0 insertions, 0 deletions
kkkkkkkkkkkkk Object ffff92fb65ec25d8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk Object ffff92fb65ec25e8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 kkkkkkkkkkkkkkk. Redzone ffff92fb65ec25f8: bb bb bb bb bb bb bb bb ........ Padding ffff92fb65ec2738: 5a 5a 5a 5a 5a 5a 5a 5a ZZZZZZZZ CPU: 3 PID: 180 Comm: kworker/3:2 Tainted: G BU 4.10.0-rc6-patser+ #5039 Hardware name: /NUC5PPYB, BIOS PYBSWCEL.86A.0031.2015.0601.1712 06/01/2015 Workqueue: events intel_atomic_helper_free_state [i915] Call Trace: dump_stack+0x4d/0x6d print_trailer+0x20c/0x220 free_debug_processing+0x1c6/0x330 ? drm_atomic_state_default_clear+0xf7/0x1c0 [drm] __slab_free+0x48/0x2e0 ? drm_atomic_state_default_clear+0xf7/0x1c0 [drm] kfree+0x159/0x1a0 drm_atomic_state_default_clear+0xf7/0x1c0 [drm] ? drm_atomic_state_clear+0x30/0x30 [drm] intel_atomic_state_clear+0xd/0x20 [i915] drm_atomic_state_clear+0x1a/0x30 [drm] __drm_atomic_state_free+0x13/0x60 [drm] intel_atomic_helper_free_state+0x5d/0x70 [i915] process_one_work+0x260/0x4a0 worker_thread+0x2d1/0x4f0 kthread+0x127/0x130 ? process_one_work+0x4a0/0x4a0 ? kthread_stop+0x120/0x120 ret_from_fork+0x29/0x40 FIX kmalloc-128: Object at 0xffff92fb65ec2578 not freed Fixes: 3b24f7d67581 ("drm/atomic: Add struct drm_crtc_commit to track async updates") Fixes: 9626014258a5 ("drm/fence: add in-fences support") Cc: <stable@vger.kernel.org> # v4.8+ Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: http://patchwork.freedesktop.org/patch/msgid/1485854725-27640-1-git-send-email-maarten.lankhorst@linux.intel.com
Diffstat (limited to 'tools/perf/tests/is_printable_array.c')