From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: apw@canonical.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] checkpatch.pl: Fix warnings on code comments
Date: Sun, 27 Jan 2013 22:07:28 -0500 (EST) [thread overview]
Message-ID: <20130127.220728.634216960903942581.davem@davemloft.net> (raw)
In-Reply-To: <1359341805.2255.56.camel@jtkirshe-mobl>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Sun, 27 Jan 2013 18:56:45 -0800
> So will you be fine with cleanup patches which go through and
> convert all the existing code comments to the desired format?
Sure.
next prev parent reply other threads:[~2013-01-28 3:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 11:35 [PATCH] checkpatch.pl: Fix warnings on code comments Jeff Kirsher
2013-01-27 17:11 ` [PATCH] checkpatch.pl: Fix warnings on (networking specific) " Joe Perches
2013-01-27 23:59 ` [PATCH] checkpatch.pl: Fix warnings on " David Miller
2013-01-28 2:56 ` Jeff Kirsher
2013-01-28 3:07 ` David Miller [this message]
2013-01-28 17:17 ` Allan, Bruce W
2013-01-28 17:30 ` Joe Perches
2013-01-28 20:56 ` Jeff Kirsher
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=20130127.220728.634216960903942581.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=apw@canonical.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).