From: Brice Goglin <brice@myri.com>
To: David Miller <davem@davemloft.net>
Cc: jeff@garzik.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] myri10ge: fix indentation
Date: Mon, 24 Nov 2008 23:52:47 +0100 [thread overview]
Message-ID: <492B303F.3080502@myri.com> (raw)
In-Reply-To: <20081124.144357.65741555.davem@davemloft.net>
David Miller wrote:
> From: Brice Goglin <brice@myri.com>
> Date: Sun, 23 Nov 2008 14:43:25 +0100
>
>
>> Bring the indentation in line with the output of the Lindent script.
>>
>> Signed-off-by: Brice Goglin <brice@myri.com>
>>
>
> Please don't blindly apply tools like this.
>
We apply indent because our internal CVS contains some #ifdef'ery to
support old kernels and we want to cleanup the mess before submitting
patches. I'll see if I can hack something here to make this struct
initializer match your will.
Brice
next prev parent reply other threads:[~2008-11-24 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 13:43 [PATCH net-next] myri10ge: fix indentation Brice Goglin
2008-11-24 22:43 ` David Miller
2008-11-24 22:52 ` Brice Goglin [this message]
2008-11-24 22:55 ` 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=492B303F.3080502@myri.com \
--to=brice@myri.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.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;
as well as URLs for NNTP newsgroup(s).