From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Eric Paris <eparis@redhat.com>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
linux-kernel@vger.kernel.org, jmorris@namei.org
Subject: Re: [PATCH 1/4] capability: capability.h whitespace, syntax, and other cleanups
Date: Thu, 24 Apr 2008 07:26:54 -0500 [thread overview]
Message-ID: <20080424122654.GA8292@sergelap.austin.ibm.com> (raw)
In-Reply-To: <1209039236.2985.127.camel@localhost.localdomain>
Quoting Eric Paris (eparis@redhat.com):
> On Wed, 2008-04-23 at 20:54 -0500, Serge E. Hallyn wrote:
> > Quoting eparis@redhat.com (eparis@redhat.com):
> > > From: Eric Paris <eparis@redhat.com>
> > >
> > > This patch changes capability.h to fix whitespace and syntax issues. Things that
> > > are fixed may include (does not not have to include)
> > >
> > > whitespace at end of lines
> > > spaces followed by tabs
> > > spaces used instead of tabs
> > > spacing around parenthesis
> > > location of { around structs and else clauses
> > > location of * in pointer declarations
> > > removal of initialization of static data to keep it in the right section
> > > useless {} in if statemetns
> > > useless checking for NULL before kfree
> > > fixing of the indentation depth of switch statements
> > > no assignments in if statements
> > > include spaces around , in function calls
> > > and any number of other things I forgot to mention
> >
> > Thanks. Looks fine other than the inexplicable (afaics)
> > jumping of the capability #s by one tab for CAP_NET_ADMIN
> > and then again from CAP_IPC_OWNER on.
>
> It just looks that way in the patch for things whose names are exactly
> that long because of the + at the beginning of the line pushing them
> over a tab column in your mailer. They are correct after the patch
> applies.
>
> > Hmm, well you also made some odd (inconsistent) tab+space choices at and
> > following cap_clear.
>
> Same thing. And I'll admit that it is a bit inconsistent, but a whole
> new tab just pushed things too far to the right and I didn't want to
> leave 8 spaces anywhere in the file. So that's what I came up with...
> I promise it looks nice in the end :)
Okay, sounds good - something needed to be done about those files in any
case. Thanks for doing that.
-serge
prev parent reply other threads:[~2008-04-24 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 17:52 eparis
2008-04-23 17:52 ` [PATCH 2/4] capability: security/capability.c " eparis
2008-04-23 17:52 ` [PATCH 3/4] capability: kernel/capability.c " eparis
2008-04-23 17:52 ` [PATCH 4/4] capability: commoncap.c " eparis
2008-04-24 1:54 ` [PATCH 1/4] capability: capability.h " Serge E. Hallyn
2008-04-24 12:13 ` Eric Paris
2008-04-24 12:26 ` Serge E. Hallyn [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=20080424122654.GA8292@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@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®