From: Dan Carpenter <dan.carpenter@oracle.com>
To: Derek Robson <robsonde@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
wsa+renesas@sang-engineering.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: ks7010: style fix, long lines
Date: Thu, 5 Jan 2017 16:21:06 +0300 [thread overview]
Message-ID: <20170105132106.GG13756@mwanda> (raw)
In-Reply-To: <20170104235616.21112-1-robsonde@gmail.com>
On Thu, Jan 05, 2017 at 12:56:16PM +1300, Derek Robson wrote:
> Debug code had very long lines.
> Reworked code to use several prints rather than one big print.
>
> Signed-off-by: Derek Robson <robsonde@gmail.com>
> ---
> drivers/staging/ks7010/ks_hostif.c | 32 +++++++++++++++++++++++++-------
> 1 file changed, 25 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/staging/ks7010/ks_hostif.c b/drivers/staging/ks7010/ks_hostif.c
> index 1fbd495e5e63..70f8565acbeb 100644
> --- a/drivers/staging/ks7010/ks_hostif.c
> +++ b/drivers/staging/ks7010/ks_hostif.c
> @@ -190,13 +190,31 @@ int get_current_ap(struct ks_wlan_private *priv, struct link_ap_info_t *ap_info)
> wireless_send_event(netdev, SIOCGIWAP, &wrqu, NULL);
> }
> DPRINTK(4, "\n Link AP\n");
> - DPRINTK(4, " bssid=%02X:%02X:%02X:%02X:%02X:%02X\n \
> - essid=%s\n rate_set=%02X,%02X,%02X,%02X,%02X,%02X,%02X,%02X\n channel=%d\n \
> - rssi=%d\n sq=%d\n capability=%04X\n", ap->bssid[0], ap->bssid[1], ap->bssid[2], ap->bssid[3], ap->bssid[4], ap->bssid[5], &(ap->ssid.body[0]), ap->rate_set.body[0], ap->rate_set.body[1], ap->rate_set.body[2], ap->rate_set.body[3], ap->rate_set.body[4], ap->rate_set.body[5], ap->rate_set.body[6], ap->rate_set.body[7], ap->channel, ap->rssi, ap->sq, ap->capability);
> - DPRINTK(4, "\n Link AP\n rsn.mode=%d\n rsn.size=%d\n",
> - ap_info->rsn_mode, ap_info->rsn.size);
> - DPRINTK(4, "\n ext_rate_set_size=%d\n rate_set_size=%d\n",
> - ap_info->ext_rate_set.size, ap_info->rate_set.size);
> + DPRINTK(4, " bssid=");
> + DPRINTK(4, "%02X:", ap->bssid[0]);
No. You can't do this. Every DPRINTK() prints the function name and
some other stuff so it would totally mess up the output.
regards,
dan carpenter
prev parent reply other threads:[~2017-01-05 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 23:56 [PATCH] Staging: ks7010: style fix, long lines Derek Robson
2017-01-05 13:21 ` Dan Carpenter [this message]
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=20170105132106.GG13756@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robsonde@gmail.com \
--cc=wsa+renesas@sang-engineering.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