From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Joe Perches <joe@perches.com>
Cc: Oliver Neukum <oneukum@suse.de>,
David Brownell <dbrownell@users.sourceforge.net>,
Greg Kroah-Hartman <gregkh@suse.de>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] usbnet: Convert dbg to dev_dbg and neatening
Date: Wed, 04 May 2011 15:35:55 +0400 [thread overview]
Message-ID: <4DC13A1B.8020004@ru.mvista.com> (raw)
In-Reply-To: <f86364fbdc335fadad003081d010843579e95765.1304445019.git.joe@perches.com>
Hello.
On 03-05-2011 22:17, Joe Perches wrote:
> Use the more standard logging form.
> Add a bit more tidying style.
Style changes look rather doubtful to me...
> Signed-off-by: Joe Perches<joe@perches.com>
> ---
> drivers/net/usb/usbnet.c | 23 +++++++++++------------
> 1 files changed, 11 insertions(+), 12 deletions(-)
> diff --git a/drivers/net/usb/usbnet.c b/drivers/net/usb/usbnet.c
> index 28aecbb..b803085 100644
> --- a/drivers/net/usb/usbnet.c
> +++ b/drivers/net/usb/usbnet.c
> @@ -192,8 +192,8 @@ static int init_status(struct usbnet *dev, struct usb_interface *intf)
> return 0;
>
> pipe = usb_rcvintpipe(dev->udev,
> - dev->status->desc.bEndpointAddress
> - & USB_ENDPOINT_NUMBER_MASK);
> + (dev->status->desc.bEndpointAddress
> + & USB_ENDPOINT_NUMBER_MASK));
Why add parens?
> @@ -1345,8 +1346,9 @@ usbnet_probe(struct usb_interface *udev, const struct usb_device_id *prod)
> dev->intf = udev;
> dev->driver_info = info;
> dev->driver_name = name;
> - dev->msg_enable = netif_msg_init(msg_level, NETIF_MSG_DRV
> - | NETIF_MSG_PROBE | NETIF_MSG_LINK);
> + dev->msg_enable = netif_msg_init(msg_level, (NETIF_MSG_DRV |
> + NETIF_MSG_PROBE |
> + NETIF_MSG_LINK));
Why add parens?
> @@ -1466,8 +1468,7 @@ EXPORT_SYMBOL_GPL(usbnet_probe);
>
> /*-------------------------------------------------------------------------*/
>
> -/*
> - * suspend the whole driver as soon as the first interface is suspended
> +/* suspend the whole driver as soon as the first interface is suspended
Why? This already corresponded to the preferred multi-line comment style...
> * resume only when the last interface is resumed
> */
>
> @@ -1485,16 +1486,14 @@ int usbnet_suspend(struct usb_interface *intf, pm_message_t message)
> set_bit(EVENT_DEV_ASLEEP,&dev->flags);
> spin_unlock_irq(&dev->txq.lock);
> }
> - /*
> - * accelerate emptying of the rx and queues, to avoid
> + /* accelerate emptying of the rx and queues, to avoid
Why?
> * having everything error out.
> */
> netif_device_detach(dev->net);
> usbnet_terminate_urbs(dev);
> usb_kill_urb(dev->interrupt);
>
> - /*
> - * reattach so runtime management can use and
> + /* reattach so runtime management can use and
Why?
WBR, Sergei
next prev parent reply other threads:[~2011-05-04 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 18:17 [PATCH 0/2] usbnet: style cleaning and logging Joe Perches
2011-05-03 18:17 ` [PATCH 1/2] usbnet: Style cleanups Joe Perches
2011-05-03 18:49 ` Oliver Neukum
2011-05-03 19:05 ` Joe Perches
2011-05-03 18:17 ` [PATCH 2/2] usbnet: Convert dbg to dev_dbg and neatening Joe Perches
2011-05-03 18:51 ` Oliver Neukum
2011-05-04 11:35 ` Sergei Shtylyov [this message]
2011-05-04 12:11 ` Joe Perches
2011-05-04 12:42 ` Michał Mirosław
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=4DC13A1B.8020004@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=dbrownell@users.sourceforge.net \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.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.