From: Joe Perches <joe@perches.com>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: netdev@vger.kernel.org, Jay Vosburgh <fubar@us.ibm.com>
Subject: Re: [PATCH net-next-2.6] bonding: reduce noise during init
Date: Tue, 26 Jul 2011 18:08:22 -0700 [thread overview]
Message-ID: <1311728902.15386.47.camel@Joe-Laptop> (raw)
In-Reply-To: <CAHashqDd8iFou7MsdCU2=2mEyaSo5RvsJoqd47jZTCwwdU81eA@mail.gmail.com>
On Tue, 2011-07-26 at 20:56 -0400, Andy Gospodarek wrote:
> On Jul 26, 2011 8:40 PM, "Joe Perches" <joe@perches.com> wrote:
> > On Tue, 2011-07-26 at 17:37 -0700, Jay Vosburgh wrote:
> > > Joe Perches <joe@perches.com> wrote:
> > > >I'd prefer you don't separate the format string
> > > >into multiple pieces.
> > > Why not? To me, it looks easier to read split into sections
> > > that don't wrap lines.
> > Harder to grep for a dmesg and the
> > defect rate of these split formats is
> > typically higher than single strings
> > because of bad spacing between string
> > segments.
> I'll agree that grepping based on dmesg/log output can be more
> difficult, but incorrect spacing should simply be fixed rather than a
> wholesale ban.
I didn't know I can ban things.
Cool. Do I get a sceptre too?
> The visual benefit when looking at the code makes this really nice, so
> I would prefer to breakup long strings when changing nearby code.
Up to you.
One other possible benefit of keeping formats
together is that if the message is overly long,
(ideally dmesg should have messages < 80 chars)
then it's more obvious that it should be somehow
shortened.
cheers, Joe
next prev parent reply other threads:[~2011-07-27 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 21:35 [PATCH net-next-2.6] bonding: reduce noise during init Andy Gospodarek
2011-07-26 21:54 ` Joe Perches
2011-07-27 0:37 ` Jay Vosburgh
2011-07-27 0:40 ` Joe Perches
2011-07-27 1:05 ` Andy Gospodarek
[not found] ` <CAHashqDd8iFou7MsdCU2=2mEyaSo5RvsJoqd47jZTCwwdU81eA@mail.gmail.com>
2011-07-27 1:08 ` Joe Perches [this message]
2011-07-27 20:09 ` [PATCH net-next-2.6 v2] " Andy Gospodarek
2011-07-28 5:40 ` 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=1311728902.15386.47.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--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