linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: add driver ops debugging
Date: Fri, 27 Mar 2009 10:47:23 +0100	[thread overview]
Message-ID: <1238147243.4331.101.camel@johannes.local> (raw)
In-Reply-To: <1238066858.4331.30.camel@johannes.local> (sfid-20090326_122819_843243_E02404BE)

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

On Thu, 2009-03-26 at 12:27 +0100, Johannes Berg wrote:
> This patch adds (optional) debugging for each driver call
> (except tx) that can print out the call, its parameters and
> the return value from the driver. I did this by adding static
> inlines for each driver operation and integrating debugging
> into them, thus all driver calls are now written as
> 
> 	drv_<op>(local, ...);
> 
> instead of
> 
> 	local->ops-><op>(&local->hw, ...);
> 
> Some of the inlines have also gotten the existence check and
> default return values for the call integrated into them.

This patch dropped some output for the no-conf_tx case that Jouni
explicitly added for that case, I have a new version on my homepage but
am looking into ftrace right now.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2009-03-27  9:47 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
2009-03-26 17:21         ` Luis R. Rodriguez
2009-03-27  9:47 ` Johannes Berg [this message]
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=1238147243.4331.101.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).