From: Andreas Dilger <adilger@sun.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: FD Cami <francois.cami@free.fr>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Kasper Sandberg <lkml@metanurb.dk>
Subject: Re: [PATCH] extX: convert prink(KERN_WARNING) to extX_warning()
Date: Tue, 24 Jun 2008 00:47:07 -0600 [thread overview]
Message-ID: <20080624064707.GF6239@webber.adilger.int> (raw)
In-Reply-To: <20080623133855.c00ddaa7.randy.dunlap@oracle.com>
On Jun 23, 2008 13:38 -0700, Randy Dunlap wrote:
> On Mon, 23 Jun 2008 14:31:07 -0600 Andreas Dilger wrote:
> > > ext3_warning(sb, __func__,
> > > - "updating to rev %d because of new feature flag, "
> > > - "running e2fsck is recommended",
> > > - EXT3_DYNAMIC_REV);
> > > + "updating to rev %d because of new feature flag, "
> > > + "running e2fsck is recommended",
> > > + EXT3_DYNAMIC_REV);
> >
> > Please don't change all of the indenting. The old indending is proper
> > linux coding style (aligned with previous '('), the new one is not.
>
> Hi,
> I don't mind which way it's done, but I'm curious: are you saying that
> aligning with '(' is codified (e.g., in CodingStyle) or just that it's
> dominant?
You're right - it isn't in the Linux CodingStyle... It is the style
that we use for Lustre that explicitly requires aligning with '('.
The common stype definitely IS to align with the previous '(' if a line
is a continuation.
That said, it is IMHO bad form to go and change all of the indenting of
existing code with little reason to do so.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-06-24 6:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 18:18 [PATCH] extX: convert prink(KERN_WARNING) to extX_warning() FD Cami
2008-06-23 20:31 ` Andreas Dilger
2008-06-23 20:34 ` Eric Sandeen
2008-06-23 20:38 ` Randy Dunlap
2008-06-24 6:47 ` Andreas Dilger [this message]
2008-06-23 22:20 ` FD Cami
2008-06-24 6:53 ` Andreas Dilger
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=20080624064707.GF6239@webber.adilger.int \
--to=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=francois.cami@free.fr \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox