From: Joe Perches <joe@perches.com>
To: Lekensteyn <lekensteyn@gmail.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
Wey-Yi Guy <wey-yi.w.guy@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: fix Oops on reading debugfs log_event
Date: Sun, 17 Jun 2012 15:05:48 -0700 [thread overview]
Message-ID: <1339970748.7577.1.camel@joe2Laptop> (raw)
In-Reply-To: <7841457.8s9HYuaGXa@penguin>
On Sun, 2012-06-17 at 22:58 +0200, Lekensteyn wrote:
> Before this patch, reading log_event would print the event log to syslog and
> crash if CONFIG_IWLWIFI_DEBUG was disabled (while CONFIG_IWLWIFI_DEBUGFS was
> enabled of course).
Make CONFIG_IWLWIFI_DEBUGFS dependent on CONFIG_IWLWIFI_DEBUG?
next prev parent reply other threads:[~2012-06-17 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 20:58 [PATCH] iwlwifi: fix Oops on reading debugfs log_event Lekensteyn
2012-06-17 22:05 ` Joe Perches [this message]
2012-06-18 7:31 ` Johannes Berg
2012-06-19 7:20 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1339970748.7577.1.camel@joe2Laptop \
--to=joe@perches.com \
--cc=ilw@linux.intel.com \
--cc=johannes.berg@intel.com \
--cc=lekensteyn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).