From: Ben Hutchings <bhutchings@solarflare.com>
To: Asbjoern Sloth Toennesen <asbjorn@asbjorn.biz>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/7] e1000e: cleanup: fix long lines
Date: Thu, 09 Dec 2010 03:34:23 +0000 [thread overview]
Message-ID: <1291865663.19763.2.camel@localhost> (raw)
In-Reply-To: <1291862457-16671-5-git-send-email-asbjorn@asbjorn.biz>
On Thu, 2010-12-09 at 02:40 +0000, Asbjoern Sloth Toennesen wrote:
> This patch breaks long lines, so they do not exceed 80 characters.
>
> Fixes 2 errors and 26 warnings reported by checkpatch.
[...]
80-character lines are not a strict requirement. The kernel coding
style is about readability, not slavishingly following rules.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-12-09 3:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 2:40 [PATCH 0/7] e1000e: cleanup Asbjoern Sloth Toennesen
2010-12-09 2:40 ` [PATCH 1/7] e1000e: cleanup: fix spacing issues Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` [PATCH 2/7] e1000e: cleanup: fix bracket issues Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` [PATCH 3/7] e1000e: cleanup: simplify E1000_ALL_* defines Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` [PATCH 4/7] e1000e: cleanup: fix long lines Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 3:34 ` Ben Hutchings [this message]
2010-12-09 2:40 ` [PATCH 5/7] e1000e: cleanup: fix space issues in ich8_* structs Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` [PATCH 6/7] e1000e: cleanup: swap arguments to avoid checkpatch errors Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 3:32 ` Ben Hutchings
2010-12-09 10:34 ` Florian Mickler
2010-12-09 2:40 ` [PATCH 7/7] e1000e: cleanup: fix copyright notices to preferred style Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 2:40 ` Asbjoern Sloth Toennesen
2010-12-09 3:37 ` [PATCH 0/7] e1000e: cleanup Stephen Hemminger
2010-12-10 5:20 ` Kirsher, Jeffrey T
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=1291865663.19763.2.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=asbjorn@asbjorn.biz \
--cc=e1000-devel@lists.sourceforge.net \
--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).