From: Stefano Brivio <stefano.brivio@polimi.it>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Michael Buesch <mb@bu3sch.de>,
Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [RFC 2/10] Port of bcm43xx from softmac to mac80211
Date: Fri, 3 Aug 2007 16:38:36 +0200 [thread overview]
Message-ID: <20070803163836.7ef9622b@morte> (raw)
In-Reply-To: <46b1fded.0g4ZHvU7XwSzeJVs%Larry.Finger@lwfinger.net>
On Thu, 02 Aug 2007 10:53:17 -0500
Larry Finger <Larry.Finger@lwfinger.net> wrote:
> +static char big_buffer[1024*256];
static char big_buffer[1024 * 256];
> + bcmerr(dev->wl, "debugfs: Board not initialized.\n");
> res = -EFAULT;
> goto out_unlock;
> }
> - if (sscanf(buf, "%lli", &tsf) != 1) {
> - printk(KERN_INFO PFX "debugfs: invalid values for
> \"tsf\"\n");
> + if (sscanf(buf, "%llu", (unsigned long long *)(&tsf)) != 1) {
> + bcmerr(dev->wl, "debugfs: invalid values for \"tsf\"\n");
"debugfs: Invalid values for TSF.\n"
> + int i;
> + int idx;
int i, idx;
> +void bcm43xx_debugfs_add_device(struct bcm43xx_wldev *dev)
> {
> struct bcm43xx_dfsentry *e;
> - char devdir[IFNAMSIZ];
> + struct bcm43xx_txstatus_log *log;
> + char devdir[16];
>
> - assert(bcm);
> + BCM43xx_BUG_ON(!dev);
> e = kzalloc(sizeof(*e), GFP_KERNEL);
> if (!e) {
> - printk(KERN_ERR PFX "out of memory\n");
> + bcmerr(dev->wl, "debugfs: add device OOM\n");
"debugfs: OOM while adding device.\n"
> + bcmerr(dev->wl, "debugfs: add device txstatus OOM\n");
"debugfs: OOM while adding device txstatus.\n"
And the same for all the debugfs messages, please be consistent.
--
Ciao
Stefano
next prev parent reply other threads:[~2007-08-03 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 15:53 [RFC 2/10] Port of bcm43xx from softmac to mac80211 Larry Finger
2007-08-03 14:38 ` Stefano Brivio [this message]
2007-08-03 15:30 ` Michael Buesch
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=20070803163836.7ef9622b@morte \
--to=stefano.brivio@polimi.it \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).