mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Lars Lindley <lindley@coyote.org>
Cc: gregkh@suse.de, greg@kroah.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: winbond: mac_structures.h Fixed indentation, whitespace etc
Date: Mon, 15 Mar 2010 20:18:05 +0100	[thread overview]
Message-ID: <20100315191804.GA23292@elf.ucw.cz> (raw)
In-Reply-To: <1268674900-9663-1-git-send-email-lindley@coyote.org>

On Mon 2010-03-15 18:41:40, Lars Lindley wrote:
> I fixed all problems reported by checkpatch.pl except typedefs.

...which only shows how little problems checkpatch detects.

> --- a/drivers/staging/winbond/mac_structures.h

> +/* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> + * MAC_Structures.h
> + *
> + * This file contains the definitions and data structures used by SW-MAC.
> + *
> + * Revision Histoy
> + * =================
> + * 0.1      2002        UN00
> + * 0.2      20021004    PD43 CCLiu6
> + *          20021018    PD43 CCLiu6
> + *                      Add enum_TxRate type
> + *                      Modify enum_STAState type
> + * 0.3      20021023    PE23 CYLiu update MAC session struct
> + *          20021108
> + *          20021122    PD43 Austin
> + *                      Deleted some unused.
> + *          20021129    PD43 Austin
> + *			20030617	increase the 802.11g
> definition

Get rid of revision history; it does not make sense, is not english,
and just should not be there.

> +/*----- Some miscellaneous definitions */
> +#define MAX_CHANNELS				30
> +#define MAC_ADDR_LENGTH				6
> +#define MAX_WEP_KEY_SIZE			16  /* 128 bits */
> +#define	MAX_802_11_FRAGMENT_NUMBER		10  /* By spec */

Consistent tabs vs spaces?

> +#define REASON_IE_DIFF_4WAY_ASSOC		17
> +#define REASON_INVALID_MULTICAST_CIPHER		18
> +#define REASON_INVALID_UNICAST_CIPHER		19
> +#define REASON_INVALID_AKMP			20
> +#define REASON_UNSUPPORTED_RSNIE_VERSION	21
> +#define REASON_INVALID_RSNIE_CAPABILITY		22
> +#define REASON_802_1X_AUTH_FAIL			23
> +#define	REASON_CIPHER_REJECT_PER_SEC_POLICY	14

Same here.

> +	// SUCCESS   = 0,      **** Redefined
> +	UNSPECIFIED_FAILURE				= 1,

I thought you was killing C++ comments?

> +struct PHY_Parameter_Set_Element {
> +/*	int	aSlotTime; */
> +/*	int	aSifsTime; */

Commented out code should be killed, not commented out in nicer way.

> +/*Authentication suite*/

Spaces after /* and before */...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2010-03-15 19:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 17:41 Lars Lindley
2010-03-15 19:18 ` Pavel Machek [this message]
2010-03-16 12:44   ` [PATCH] staging: winbond: mac_structures.h Fix remaining whitespace and comment issues Lars Lindley
2010-04-28 22:48     ` Greg KH
2010-03-15 20:17 ` [PATCH] staging: winbond: mac_structures.h Fixed indentation, whitespace etc Pavel Machek

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=20100315191804.GA23292@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=lindley@coyote.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®