DO NOT ADD FIRMWARE TO THIS DIRECTORY. ====================================== This directory is only here to contain firmware images extracted from old device drivers which predate the common use of request_firmware(). As we update those drivers to use request_firmware() and keep a clean separation between code and firmware, we put the extracted firmware here. This directory is _NOT_ for adding arbitrary new firmware images. The place to add those is the separate linux-firmware repository: git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git That repository contains all these firmware images which have been extracted from older drivers, as well various new firmware images which we were never permitted to include in a GPL'd work, but which we _have_ been permitted to redistribute under separate cover. To submit firmware to that repository, please send either a git binary diff or preferably a git pull request to: linux-firmware@kernel.org and also cc: to related mailing lists. Your commit should include an update to the WHENCE file clearly identifying the licence under which the firmware is available, and that it is redistributable. If the licence is long and involved, it's permitted to include it in a separate file and refer to it from the WHENCE file. And if it were possible, a changelog of the firmware itself. Ideally, your commit should contain a Signed-Off-By: from someone authoritative on the licensing of the firmware in question (i.e. from within the company that owns the code). WARNING: ======= Don't send any "CONFIDENTIALITY STATEMENT" in your e-mail, patch or request. Otherwise your firmware _will never be accepted_. Maintainers are really busy, so don't expect a prompt reply. next.git/tree/net/sched/act_vlan.c?id=0becc0ae5b42828785b589f686725ff5bc3b9b25'>treecommitdiff
path: root/net/sched/act_vlan.c
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2017-01-31 09:37:34 +0100
committerThomas Gleixner <tglx@linutronix.de>2017-01-31 21:47:58 +0100
commit0becc0ae5b42828785b589f686725ff5bc3b9b25 (patch)
treebe6d0e1f37c38ed0a7dd5da2d4b1e93f0fb43101 /net/sched/act_vlan.c
parent24c2503255d35c269b67162c397a1a1c1e02f6ce (diff)
x86/mce: Make timer handling more robust
Erik reported that on a preproduction hardware a CMCI storm triggers the BUG_ON in add_timer_on(). The reason is that the per CPU MCE timer is started by the CMCI logic before the MCE CPU hotplug callback starts the timer with add_timer_on(). So the timer is already queued which triggers the BUG. Using add_timer_on() is pretty pointless in this code because the timer is strictlty per CPU, initialized as pinned and all operations which arm the timer happen on the CPU to which the timer belongs. Simplify the whole machinery by using mod_timer() instead of add_timer_on() which avoids the problem because mod_timer() can handle already queued timers. Use __start_timer() everywhere so the earliest armed expiry time is preserved. Reported-by: Erik Veijola <erik.veijola@intel.com> Tested-by: Borislav Petkov <bp@alien8.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Borislav Petkov <bp@alien8.de> Cc: Tony Luck <tony.luck@intel.com> Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1701310936080.3457@nanos Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'net/sched/act_vlan.c')