From: Johannes Berg <johannes@sipsolutions.net>
To: Bob Copeland <me@bobcopeland.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: add driver ops debugging
Date: Thu, 26 Mar 2009 16:33:59 +0100 [thread overview]
Message-ID: <1238081639.4331.63.camel@johannes.local> (raw)
In-Reply-To: <b6c5339f0903260826t58c8c595ve612fa35ba7c91e4@mail.gmail.com> (sfid-20090326_162639_619200_70BA77E4)
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On Thu, 2009-03-26 at 11:26 -0400, Bob Copeland wrote:
> On Thu, Mar 26, 2009 at 10:46 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> >> Could we use some newfangled thing like tracepoints for this
> >> instead of printk? Disclaimer: I know nothing about such
> >> things.
> >
> > Probably. Want to look at how to do that? :)
>
> Sure, I'll do some research and see what's involved. Don't hold
> up the patch on my account though.
Oh doesn't matter to me -- I was posting it more because I did it, I
don't have an immediate need to have it included. If you want to take
some time to look into that we can hold the patch without any trouble, I
agree it would probably be nicer, just didn't work with any of that
stuff before so I didn't even think of it.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-26 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 11:27 [PATCH] mac80211: add driver ops debugging Johannes Berg
2009-03-26 14:41 ` Bob Copeland
2009-03-26 14:46 ` Johannes Berg
2009-03-26 15:26 ` Bob Copeland
2009-03-26 15:33 ` Johannes Berg [this message]
2009-03-26 17:21 ` Luis R. Rodriguez
2009-03-27 9:47 ` Johannes Berg
2009-03-28 11:12 ` Jouni Malinen
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=1238081639.4331.63.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.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).