From: Petko Manolov <petkan@nucleusys.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] drivers: net: usb: rtl8150: making the code a bit better looking
Date: Mon, 20 May 2013 22:16:33 +0300 (EEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1305202208460.3400@fry.nucleusys.com> (raw)
In-Reply-To: <1369061535.4616.2.camel@bwh-desktop.uk.solarflarecom.com>
On Mon, 20 May 2013, Ben Hutchings wrote:
> [...]
> > @@ -771,12 +770,12 @@ static void rtl8150_disconnect(struct usb_interface *intf)
> > }
> >
> > static struct usb_driver rtl8150_driver = {
> > - .name = driver_name,
> > - .probe = rtl8150_probe,
> > - .disconnect = rtl8150_disconnect,
> > - .id_table = rtl8150_table,
> > - .suspend = rtl8150_suspend,
> > - .resume = rtl8150_resume,
> > + .name = driver_name,
> > + .probe = rtl8150_probe,
> > + .disconnect = rtl8150_disconnect,
> > + .id_table = rtl8150_table,
> > + .suspend = rtl8150_suspend,
> > + .resume = rtl8150_resume,
> > .disable_hub_initiated_lpm = 1,
> > };
>
> These looked better before. Lining up initialisers in a structure
> definition is good style.
It is. This is what i usually do. However, scripts/Lindent is messed up
in (not only) this regard. IMHO it should not be used as it is.
I thought using what is recommended (at least in the documentation) makes
me a good citizen even though i don't like the end result much.
Again, the above is true in case i've not misunderstood something,
somewhere.
Petko
prev parent reply other threads:[~2013-05-20 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 20:21 Petko Manolov
2013-05-20 14:52 ` Ben Hutchings
2013-05-20 19:16 ` Petko Manolov [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=alpine.DEB.2.02.1305202208460.3400@fry.nucleusys.com \
--to=petkan@nucleusys.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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®