Your commit aadede6e9f4c (iwlwifi: mvm: port to devcoredump framework)
landed in today's linux-next (next-20141031). It adds a select statement
for BACKPORT_WANT_DEV_COREDUMP. There's no Kconfig symbol
BACKPORT_WANT_DEV_COREDUMP so this select is currently a nop. (In
On Fri, 2014-10-31 at 09:45 +0100, Johannes Berg wrote:
On Fri, 2014-10-31 at 09:40 +0100, Paul Bolle wrote:
Your commit aadede6e9f4c (iwlwifi: mvm: port to devcoredump framework)
landed in today's linux-next (next-20141031). It adds a select statement
for BACKPORT_WANT_DEV_COREDUMP.
On Fri, 2014-10-31 at 10:06 +0100, Paul Bolle wrote:
On Fri, 2014-10-31 at 09:45 +0100, Johannes Berg wrote:
On Fri, 2014-10-31 at 09:40 +0100, Paul Bolle wrote:
Your commit aadede6e9f4c (iwlwifi: mvm: port to devcoredump framework)
landed in today's linux-next (next-20141031). It adds a
On Fri, 2014-10-31 at 10:08 +0100, Johannes Berg wrote:
On Fri, 2014-10-31 at 10:06 +0100, Paul Bolle wrote:
Perhaps you could also look into somehow guarding the call of
dev_coredumpm(), that this commit added, with checks for
CONFIG_DEV_COREDUMP. See, I had a quick look at all this and
