[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1359394228.31480.7.camel@joe-AO722>
Date: Mon, 28 Jan 2013 09:30:28 -0800
From: Joe Perches <joe@...ches.com>
To: "Allan, Bruce W" <bruce.w.allan@...el.com>
Cc: David Miller <davem@...emloft.net>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"apw@...onical.com" <apw@...onical.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] checkpatch.pl: Fix warnings on code comments
On Mon, 2013-01-28 at 17:17 +0000, Allan, Bruce W wrote:
> David Miller Sent: Sunday, January 27, 2013 7:07 PM
> > From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> > > So will you be fine with cleanup patches which go through and
> > > convert all the existing code comments to the desired format?
> > Sure.
> Not all Intel drivers...e1000e already conforms to the comment style :-)
In case anyone cares, here's a perl regex
to do network comment style conversion.
$text =~ s@/\*[ \t]*\n[ \t]*\*@/*@g;
$text =~ s@/\*([ \t]*)([^\n]+)\n[ \t]*\*/@/\*$1$2 \*/@g;
(assumes the entire file is in $text)
It creates a ~220KB diff for drivers/net/ethernet/intel/
that I won't post.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists