From: Greg KH <gregkh@suse.de>
To: Neil Munro <neilmunro@gmail.com>
Cc: wfp5p@virginia.edu, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1586/1586] Staging: RT2860: Fixed my previous patch.
Date: Thu, 20 May 2010 08:06:44 -0700 [thread overview]
Message-ID: <20100520150644.GA3862@suse.de> (raw)
In-Reply-To: <1274354933-24377-1-git-send-email-neilmunro@gmail.com>
On Thu, May 20, 2010 at 12:28:53PM +0100, Neil Munro wrote:
> From: Niadh <neilmunro@gmail.com>
>
> I have corrected the confusion between braces and parethesis. In
> addition I have removed a few warnings where the lines were over 80
> lines and finaly have implemented a few suggestions Joe Perches
> suggested (thanks Joe).
>
> Signed-off-by: Neil Munro <neilmunro@gmail.com>
> ---
> drivers/staging/rt2860/mlme.h | 89 +++++++++++++++++++++++++----------------
> 1 files changed, 55 insertions(+), 34 deletions(-)
>
> diff --git a/drivers/staging/rt2860/mlme.h b/drivers/staging/rt2860/mlme.h
> index 63cada3..02cbe9a 100644
> --- a/drivers/staging/rt2860/mlme.h
> +++ b/drivers/staging/rt2860/mlme.h
> @@ -31,7 +31,7 @@
>
> Revision History:
> Who When What
> - -------- ---------- ----------------------------------------------
> + -------- ---------- ------------
> John Chang 2003-08-28 Created
> John Chang 2004-09-06 modified for RT2600
>
> @@ -49,8 +49,9 @@
> #define LFSR_MASK 0x80000057
> #define MLME_TASK_EXEC_INTV 100/*200*/ /* */
> #define LEAD_TIME 5
> -#define MLME_TASK_EXEC_MULTIPLE 10 /*5*/ /* MLME_TASK_EXEC_MULTIPLE * MLME_TASK_EXEC_INTV = 1 sec */
> -#define REORDER_EXEC_INTV 100 /* 0.1 sec */
> +#define MLME_TASK_EXEC_MULTIPLE 10
> +/*5*/ /* MLME_TASK_EXEC_MULTIPLE * MLME_TASK_EXEC_INTV = 1 sec */
This doesn't make sense. Put the comment on the line before.
And drop the /*5*/, it too doesn't make sense.
> +#define REORDER_EXEC_INTV 100 /* 0.1 sec */
>
> /* The definition of Radar detection duration region */
> #define CE 0
> @@ -60,7 +61,7 @@
> #define JAP_W56 4
> #define MAX_RD_REGION 5
>
> -#define BEACON_LOST_TIME { 4 * OS_HZ } /* 2048 msec = 2 sec */
> +#define BEACON_LOST_TIME (4 * OS_HZ) /* 2048 msec = 2 sec */
As I didn't take your original patch, this patch will not apply. Please
generate a new patch that I can apply properly to the linux-next tree.
thanks,
greg k-h
prev parent reply other threads:[~2010-05-20 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 11:28 [PATCH 1586/1586] Staging: RT2860: Fixed my previous patch Neil Munro
2010-05-20 15:06 ` Greg KH [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=20100520150644.GA3862@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilmunro@gmail.com \
--cc=wfp5p@virginia.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.