From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
Cc: devel@driverdev.osuosl.org, Matti Lammi <mattij.lammi@gmail.com>,
gregkh@suse.de, andrea.gelmini@gelma.net,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rt3070: Fixed a line over 80 character warning reported by checkpatch.pl tool
Date: Sun, 13 Jun 2010 12:42:41 +0200 [thread overview]
Message-ID: <201006131242.41512.bzolnier@gmail.com> (raw)
In-Reply-To: <201006101521.45409.s.L-H@gmx.de>
Hi,
On Thursday 10 June 2010 03:21:42 pm Stefan Lippers-Hollmann wrote:
> Hi
>
> On Thursday 10 June 2010, Matti Lammi wrote:
> > Divided a comment line into two separet lines in drivers/staging/rt3070/md4.h.
>
> Isn't drivers/staging/rt3070/ as a whole dead code by now? What about the
> following removal patch instead (compile tested and no complaints from
> rt30[79]0 users yet)?
Looks fine to me, FWIW:
Acked-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> As a side note, rt2800pci/ rt2800usb from drivers/net/wireless/rt2x00/ have
> become fully functional for rt2770, rt2860, rt2870 (and I've gotten
> very positive feedback for rt3070/ rt3090) with 2.6.35, so the staging
> rt2860/ rt2870 drivers could be removed soon (now?). rt35xx support is
> rt2x00-only anyways and HT rates aren't actually achievable by staging
> (only by newer out-of-tree vendor drivers) or rt2x00 (work is under way)
> yet.
No idea here. The last time I tried rt2800 drivers was in 2.6.34-rc days
and my experiences were not exactly positive back then. Things may be
different nowadays or they may be not -- I don't have any time to spend on
this and staging drivers continue to work just fine for me at the moment.
> From: Stefan Lippers-Hollmann <s.l-h@gmx.de>
> Date: Wed, 24 Mar 2010 20:56:13 +0000
> Subject: [PATCH] rt3070: remove dead code
>
> While merging rt30[79]0 support into rt28[67]0, drivers/staging/rt3070/md4.h
> has been forgotten, while it isn't referenced from the remaining drivers
> anymore; remove it.
>
> Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
> ---
> drivers/staging/rt3070/md4.h | 42 ------------------------------------------
> 1 files changed, 0 insertions(+), 42 deletions(-)
> delete mode 100644 drivers/staging/rt3070/md4.h
>
> diff --git a/drivers/staging/rt3070/md4.h b/drivers/staging/rt3070/md4.h
> deleted file mode 100644
> index b3fb637..0000000
> --- a/drivers/staging/rt3070/md4.h
> +++ /dev/null
> @@ -1,42 +0,0 @@
> -/*
> - *************************************************************************
> - * Ralink Tech Inc.
> - * 5F., No.36, Taiyuan St., Jhubei City,
> - * Hsinchu County 302,
> - * Taiwan, R.O.C.
> - *
> - * (c) Copyright 2002-2007, Ralink Technology, Inc.
> - *
> - * This program is free software; you can redistribute it and/or modify *
> - * it under the terms of the GNU General Public License as published by *
> - * the Free Software Foundation; either version 2 of the License, or *
> - * (at your option) any later version. *
> - * *
> - * This program is distributed in the hope that it will be useful, *
> - * but WITHOUT ANY WARRANTY; without even the implied warranty of *
> - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the *
> - * GNU General Public License for more details. *
> - * *
> - * You should have received a copy of the GNU General Public License *
> - * along with this program; if not, write to the *
> - * Free Software Foundation, Inc., *
> - * 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. *
> - * *
> - *************************************************************************
> - */
> -
> -#ifndef __MD4_H__
> -#define __MD4_H__
> -
> -/* MD4 context. */
> -typedef struct _MD4_CTX_ {
> - unsigned long state[4]; /* state (ABCD) */
> - unsigned long count[2]; /* number of bits, modulo 2^64 (lsb first) */
> - u8 buffer[64]; /* input buffer */
> -} MD4_CTX;
> -
> -void MD4Init(MD4_CTX *);
> -void MD4Update(MD4_CTX *, u8 *, UINT);
> -void MD4Final(u8 [16], MD4_CTX *);
> -
> -#endif /*__MD4_H__*/
--
Bartlomiej Zolnierkiewicz
prev parent reply other threads:[~2010-06-13 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 10:00 [PATCH] rt3070: Fixed a line over 80 character warning reported by checkpatch.pl tool Matti Lammi
2010-06-10 13:21 ` Stefan Lippers-Hollmann
2010-06-13 10:42 ` Bartlomiej Zolnierkiewicz [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=201006131242.41512.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=andrea.gelmini@gelma.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mattij.lammi@gmail.com \
--cc=s.L-H@gmx.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 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.