From: Ondrej Zary <linux@rainbow-software.org>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: "Greg Kroah-Hartman" <greg@kroah.com>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC, RFT] [PATCH] staging: ft1000: unify struct ft1000_info between USB and PCMCIA drivers
Date: Tue, 13 Nov 2012 11:11:38 +0100 [thread overview]
Message-ID: <201211131111.38721.linux@rainbow-software.org> (raw)
In-Reply-To: <CAAfyv36UhwVmjwBV5RKDmWm3ag_yqr+t1u+NHAtamFSkmcrUhw@mail.gmail.com>
On Monday 12 November 2012, Belisko Marek wrote:
> Hi Ondrej,
>
> On Fri, Nov 9, 2012 at 10:42 PM, Ondrej Zary <linux@rainbow-software.org>
wrote:
> > Unify struct ft1000_info between ft1000-usb and ft1000-pcmcia and move it
> > to common ft1000.h.
> >
> > ft1000-pcmcia seems to work. Please test ft1000-usb.
> >
> > Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
> > ---
> > drivers/staging/ft1000/ft1000-pcmcia/ft1000.h | 33 +-----
> > drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c | 21 ++-
> > drivers/staging/ft1000/ft1000-pcmcia/ft1000_proc.c | 10 +-
> > drivers/staging/ft1000/ft1000-usb/ft1000_debug.c | 147
> > ++++++++++---------- .../staging/ft1000/ft1000-usb/ft1000_download.c |
> > 70 +++++----- drivers/staging/ft1000/ft1000-usb/ft1000_hw.c | 99
> > +++++++------- drivers/staging/ft1000/ft1000-usb/ft1000_proc.c | 4
> > +-
> > drivers/staging/ft1000/ft1000-usb/ft1000_usb.c | 30 ++--
> > drivers/staging/ft1000/ft1000-usb/ft1000_usb.h | 54 +------
> > drivers/staging/ft1000/ft1000.h | 35 +++++
> > 10 files changed, 236 insertions(+), 267 deletions(-)
> >
> > diff --git a/drivers/staging/ft1000/ft1000-pcmcia/ft1000.h
> > b/drivers/staging/ft1000/ft1000-pcmcia/ft1000.h index adb436e..65f7ab6
> > 100644
> > --- a/drivers/staging/ft1000/ft1000-pcmcia/ft1000.h
> > +++ b/drivers/staging/ft1000/ft1000-pcmcia/ft1000.h
> > @@ -31,41 +31,10 @@
> > #define SUCCESS 0x00
> > #define FAILURE 0x01
> >
> > -struct ft1000_info {
> > - struct net_device_stats stats;
> > - u16 DrvErrNum;
> > - u16 AsicID;
> > +struct ft1000_pcmcia {
>
> To be consistent can you please name also usb part not ft100_device
> but e.g. ft1000_usb or something?
Yes, that's a good idea. I'd like to do that in a separate patch, this one is
already big enough.
> > @@ -1179,8 +1179,6 @@ static int ft1000_open(struct net_device *dev)
> > struct ft1000_info *pInfo = netdev_priv(dev);
> > struct timeval tv;
> >
> > - DEBUG("ft1000_open is called for card %d\n", pInfo->CardNumber);
>
> ^^^ Why removing this debug?
I don't remember exactly (this is from an old patch) but probably because I
didn't want to add code to reach CardNumber (which should be removed too).
The debug messages are a mess, some are completely useless, some should be
non-debug instead.
If you have the USB hardware, please test if this patch does not break
anything. I have only a PCMCIA card.
--
Ondrej Zary
next prev parent reply other threads:[~2012-11-13 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 21:42 [RFC, RFT] [PATCH] staging: ft1000: unify struct ft1000_info between USB and PCMCIA drivers Ondrej Zary
2012-11-12 22:36 ` Belisko Marek
2012-11-13 10:11 ` Ondrej Zary [this message]
2012-11-13 11:32 ` Belisko Marek
2012-11-30 23:16 ` Belisko Marek
-- strict thread matches above, loose matches on Subject: below --
2011-06-26 20:48 Ondrej Zary
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=201211131111.38721.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.belisko@gmail.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