From: Dan Carpenter <error27@gmail.com>
To: Jason Dreisbach <jtdreisb@gmail.com>
Cc: jt@hp1.hp.com, gregkh@suse.de--to, jpirko@redhat.com,
linville@tuxdriver.com, jtdreisb@gmail.com--cc,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] staging: wavelan: fix coding style of first 1000 lines in wavelan.c
Date: Mon, 8 Mar 2010 19:02:50 +0300 [thread overview]
Message-ID: <20100308160250.GC19256@bicker> (raw)
In-Reply-To: <1268043630-5893-1-git-send-email-jtdreisb@gmail.com>
On Mon, Mar 08, 2010 at 02:20:30AM -0800, Jason Dreisbach wrote:
> From: Jason <jtdreisb@gmail.com>
> /* Check mc_config command */
> if ((status & AC_SFLD_OK) != AC_SFLD_OK)
> printk(KERN_INFO
> - "%s: wv_config_complete(): set_multicast_address failed; status = 0x%x\n",
> + "%s: wv_config_complete(): \
> + set_multicast_address failed; status = 0x%x\n",
> dev->name, status);
>
This patch introduces several bugs like the one above.
I know it's depressing to send a patch and have criticized, but besides
this bug which affects users there are some other whitespace changes
in this patch which are not correct.
If you want to resend this once you fix the errors, feel free, it does
fix quite a few white space issues.
But really it's always better to focus on fixing actual bugs. I know that
Greg says fixing white space is a great way to learn the patch submission
process, but anyone can do that. The most important thing is to learn how
to fix bugs. We can deal with malformed patches so long as they fix
something.
regards,
dan carpenter
next prev parent reply other threads:[~2010-03-08 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 10:20 [PATCH] staging: wavelan: fix coding style of first 1000 lines in wavelan.c Jason Dreisbach
2010-03-08 16:02 ` Dan Carpenter [this message]
2010-03-08 16:54 ` Joe Perches
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=20100308160250.GC19256@bicker \
--to=error27@gmail.com \
--cc=gregkh@suse.de--to \
--cc=jpirko@redhat.com \
--cc=jt@hp1.hp.com \
--cc=jtdreisb@gmail.com \
--cc=jtdreisb@gmail.com--cc \
--cc=linux-kernel@vger.kernel.org \
--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