tracing: Fix hwlat kthread migration

The hwlat tracer creates a kernel thread at start of the tracer. It is
pinned to a single CPU and will move to the next CPU after each period of
running. If the user modifies the migration thread's affinity, it will not
change after that happens.

The original code created the thread at the first instance it was called,
but later was changed to destroy the thread after the tracer was finished,
and would not be created until the next instance of the tracer was
established. The code that initialized the affinity was only called on the
initial instantiation of the tracer. After that, it was not initialized, and
the previous affinity did not match the current newly created one, making
it appear that the user modified the thread's affinity when it did not, and
the thread failed to migrate again.

Cc: stable@vger.kernel.org
Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs")
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

path: root/net/irda/irlan/Kconfig

config IRLAN
	tristate "IrLAN protocol"
	depends on IRDA
	help
	  Say Y here if you want to build support for the IrLAN protocol.
	  To compile it as a module, choose M here: the module will be called
	  irlan.  IrLAN emulates an Ethernet and makes it possible to put up
	  a wireless LAN using infrared beams.

	  The IrLAN protocol can be used to talk with infrared access points
	  like the HP NetbeamIR, or the ESI JetEye NET.  You can also connect
	  to another Linux machine running the IrLAN protocol for ad-hoc
	  networking!