public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Simon Wood <simon@mungewell.org>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	linux-usb@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	David Brownell <david-b@pacbell.net>
Subject: Re: [PATCH] pl25a1_support
Date: Wed, 30 Mar 2011 15:31:36 +0400	[thread overview]
Message-ID: <4D931498.9000505@ru.mvista.com> (raw)
In-Reply-To: <1301456667-1648-1-git-send-email-simon@mungewell.org>

Hello.

On 30-03-2011 7:44, Simon Wood wrote:

> Adds support for 'Windows Easy Transfer' cables based around the
> Prolific PL-25A1 chip (includes Belkin F5U258&  F5U279)

> Patch originally suggested by David Brownell here:
> http://www.mail-archive.com/netdev@vger.kernel.org/msg61926.html

> Modified to work with latest kernel, tested with F5U279.
>
> Signed-off-by: Simon Wood<simon@mungewell.org>

[...]

> diff --git a/drivers/net/usb/plusb.c b/drivers/net/usb/plusb.c
> index 08ad269..a20afac 100644
> --- a/drivers/net/usb/plusb.c
> +++ b/drivers/net/usb/plusb.c
[...]
> @@ -89,13 +97,17 @@ static int pl_reset(struct usbnet *dev)
>   	/* some units seem to need this reset, others reject it utterly.
>   	 * FIXME be more like "naplink" or windows drivers.
>   	 */
> -	(void) pl_set_QuickLink_features(dev,
> +	int     status;
> +
> +        status = pl_set_QuickLink_features(dev,

    This line is indented with spaces ISO tab.

> +	if (status != 0 && netif_msg_probe(dev))
> +		netif_dbg(dev, link, dev->net, "pl_reset --> %d\n", status);
>  	return 0;
>  }

    Also, the above change doesn't seem to be related to the declared purpose 
of the patch, so seems to be a matter of another patch...

> @@ -134,16 +153,16 @@ static struct usb_driver plusb_driver = {
>
>   static int __init plusb_init(void)
>   {
> - 	return usb_register(&plusb_driver);
> +	return usb_register(&plusb_driver);
>   }
>   module_init(plusb_init);
>
>   static void __exit plusb_exit(void)
>   {
> - 	usb_deregister(&plusb_driver);
> +	usb_deregister(&plusb_driver);
>   }

    Likewise, the whitespace fixes should be a matgter of a separate patch...

WBR, Sergei

  parent reply	other threads:[~2011-03-30 11:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30  3:44 [PATCH] pl25a1_support Simon Wood
2011-03-30  9:40 ` David Miller
2011-03-30 11:31 ` Sergei Shtylyov [this message]
2011-04-06  4:16 ` [PatchV2 : PL25A1 Support - 1/3] whitespace Simon Wood
2011-04-06 20:17   ` David Miller
2011-04-06  4:16 ` [PatchV2 : PL25A1 Support - 2/3] add_pl25a1 Simon Wood
2011-04-06  4:16 ` [PatchV2 : PL25A1 Support - 3/3] reset_debug Simon Wood
2011-04-07  7:40 ` [PatchV3 1/3] usb: plusb: Whitespace Simon Wood
2011-04-07  7:40   ` [PatchV3 2/3] usb: plusb: Add support for PL-25A1 Simon Wood
2011-04-11  1:47     ` David Miller
2011-04-07  7:40   ` [PatchV3 3/3] usb: plusb: Add debug to reset function Simon Wood
2011-04-11  1:47     ` David Miller
2011-04-11  1:47   ` [PatchV3 1/3] usb: plusb: Whitespace David Miller

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=4D931498.9000505@ru.mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=david-b@pacbell.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=simon@mungewell.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