[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1360479151.26127.5.camel@joe-AO722>
Date: Sat, 09 Feb 2013 22:52:31 -0800
From: Joe Perches <joe@...ches.com>
To: Jean Sacren <sakiwit@...il.com>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH] skbuff: create skb_panic() to let caller specify panic
On Sat, 2013-02-09 at 23:40 -0700, Jean Sacren wrote:
> From: Joe Perches <joe@...ches.com>
> Date: Sat, 09 Feb 2013 22:02:53 -0800
> >
> > On Sat, 2013-02-09 at 22:56 -0700, Jean Sacren wrote:
> > > From: Joe Perches <joe@...ches.com>
> > > > Don't split the format across multiple lines please.
> > []
> > > Honestly I didn't want to split the whole string, but I was in the
> > > dilemma of accommodating 80-column convention. I'm ready to respin if
> > > the consensus favors one long string. But how long is too long?
> >
> > Documentation/CodingStyle
> >
> > Chapter 2: Breaking long lines and strings
> > ...
> > never break user-visible strings such as printk messages,
> > because that breaks the ability to grep for them
>
> I appreciate you for sharing this document with me, but this scenario is
> unique, as it concerns panic. Under this circumstance, are we able to
> grep?
On another machine? In a vm? I don't see why not.
Does it matter? Probably not.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists