From: Joe Perches <joe@perches.com>
To: "Williams, Mitch A" <mitch.a.williams@intel.com>
Cc: "Brown, Aaron F" <aaron.f.brown@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"gospo@redhat.com" <gospo@redhat.com>,
"sassmann@redhat.com" <sassmann@redhat.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Subject: Re: [net-next 05/14] i40evf: fix up strings in init task
Date: Fri, 14 Feb 2014 16:05:55 -0800 [thread overview]
Message-ID: <1392422755.12157.8.camel@joe-AO722> (raw)
In-Reply-To: <AAEA33E297BCAC4B9BB20A7C2DF0AB8D65517F5F@FMSMSX113.amr.corp.intel.com>
On Fri, 2014-02-14 at 23:53 +0000, Williams, Mitch A wrote:
> With regard to periods on the end of log messages,
> is this a hard rule?
No.
> The grammar pedant in me likes to see periods on the end of sentences,
Opinions vary.
I think kernel logging output lines aren't sentences
and are just notifications that don't need periods.
If you look at a normal log, there are relatively few
entries with periods.
For instance, my current dmesg:
$ dmesg | wc -l
1568
$ dmesg | grep "[^\.]\.$" | wc -l
84
next prev parent reply other threads:[~2014-02-15 0:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 22:57 [net-next 00/14] Intel Wired LAN Driver Updates Aaron Brown
2014-02-14 22:57 ` [net-next 01/14] i40evf: request reset on tx hang Aaron Brown
2014-02-14 22:57 ` [net-next 02/14] i40evf: remove VLAN filters on close Aaron Brown
2014-02-14 22:57 ` [net-next 03/14] i40evf: fix multiple crashes on remove Aaron Brown
2014-02-14 22:57 ` [net-next 04/14] i40evf: get rid of pci_using_dac Aaron Brown
2014-02-14 22:57 ` [net-next 05/14] i40evf: fix up strings in init task Aaron Brown
2014-02-14 23:43 ` Joe Perches
2014-02-14 23:53 ` Williams, Mitch A
2014-02-15 0:05 ` Joe Perches [this message]
2014-02-14 22:58 ` [net-next 06/14] i40evf: remove bogus comment Aaron Brown
2014-02-14 22:58 ` [net-next 07/14] i40evf: don't guess device name Aaron Brown
2014-02-14 22:58 ` [net-next 08/14] i40evf: store ring size in ring structs Aaron Brown
2014-02-16 9:13 ` Govindarajulu Varadarajan
2014-02-14 22:58 ` [net-next 09/14] i40evf: update version and copyright date Aaron Brown
2014-02-14 22:58 ` [net-next 10/14] i40evf: remove errant space Aaron Brown
2014-02-14 22:58 ` [net-next 11/14] i40e: remove unnecessary delay Aaron Brown
2014-02-14 22:58 ` [net-next 12/14] i40e: tighten up ring enable/disable flow Aaron Brown
2014-02-14 22:58 ` [net-next 13/14] i40e: Change MSIX to MSI-X Aaron Brown
2014-02-14 22:58 ` [net-next 14/14] i40e and i40evf: Bump driver versions Aaron Brown
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=1392422755.12157.8.camel@joe-AO722 \
--to=joe@perches.com \
--cc=aaron.f.brown@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
/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