From: Dave Feustel <dfeustel@verizon.net>
To: xen-devel@lists.xensource.com
Cc: harry <harry@hebutterworth.freeserve.co.uk>,
Vincent Hanquez <vincent.hanquez@cl.cam.ac.uk>
Subject: Re: USB virt 2.6 split driver patch series
Date: Mon, 21 Nov 2005 09:29:57 -0500 [thread overview]
Message-ID: <200511210929.57642.dfeustel@verizon.net> (raw)
In-Reply-To: <1132581661.31295.134.camel@localhost.localdomain>
On Monday 21 November 2005 09:01, harry wrote:
> On Mon, 2005-11-21 at 14:49 +0100, Vincent Hanquez wrote:
> > On Mon, Nov 21, 2005 at 01:18:24PM +0000, harry wrote:
> > > o - I've reformatted all the code to the kernel coding style using
> > > Lindent and not attempted to improve it after that. Some of the
> > > formatting needs to be improved.
> >
> > some ? this is totally _not_ linux kernel coding style.
> > please have a look at Documentation/CodingStyle and kill anonymous
> > inline functions (braces in middle of functions).
> >
>
> I have read Documentation/CodingStyle quite carefully and there is no
> mention of using braces inside functions. I'm used to using braces to
> define minimal scopes for local variables which makes the code easier to
> read by minimising the number of variables you need to keep track of
> when reading it and by declaring variables closer to where they are used
> so it is easier to verify that they have been correctly initialised.
>
> Is this really banned?
I thought braces defined code blocks, not internal functions.
Without a label the code can be invoked only inline.
Dave Feustel
> Harry.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Switch to Secure OpenBSD with a KDE desktop!!!
NOW with Virtual PC OS support via QEMU and
Beowulf clustering using PETSc and MPICH2!
next prev parent reply other threads:[~2005-11-21 14:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 13:18 USB virt 2.6 split driver patch series harry
2005-11-21 13:49 ` Vincent Hanquez
2005-11-21 14:01 ` harry
2005-11-21 14:27 ` Vincent Hanquez
2005-11-21 14:29 ` Dave Feustel [this message]
2005-11-21 14:41 ` NAHieu
2005-11-21 15:14 ` harry
2005-11-21 15:27 ` NAHieu
2005-11-21 15:39 ` harry
2005-11-21 17:02 ` NAHieu
2005-11-21 17:17 ` harry
2005-11-22 1:59 ` NAHieu
2005-11-22 2:00 ` NAHieu
2005-11-22 10:24 ` harry
2005-11-22 11:07 ` Vincent Hanquez
2005-11-22 15:37 ` Anthony Liguori
2005-11-22 20:27 ` Vincent Hanquez
2005-11-21 15:44 ` Muli Ben-Yehuda
2005-11-21 18:49 ` Harry Butterworth
2005-11-21 18:58 ` Muli Ben-Yehuda
2005-11-25 19:16 ` harry
2005-11-21 17:26 ` Oleg Goldshmidt
2005-11-21 15:34 ` harry
2005-11-21 14:25 ` Dave Feustel
2005-11-21 14:36 ` Vincent Hanquez
2005-11-21 15:24 ` Dave Feustel
2005-11-21 16:03 ` Vincent Hanquez
2005-11-21 16:30 ` Dave Feustel
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=200511210929.57642.dfeustel@verizon.net \
--to=dfeustel@verizon.net \
--cc=dfeustel@mindspring.com \
--cc=harry@hebutterworth.freeserve.co.uk \
--cc=vincent.hanquez@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 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.