From: Sami Kerola <kerolasa@iki.fi>
To: util-linux@vger.kernel.org
Cc: Sami Kerola <kerolasa@iki.fi>
Subject: [PATCH 0/5] pull: one dmesg compiler warning fix and bunch of tests
Date: Sun, 22 Mar 2015 23:05:25 +0000 [thread overview]
Message-ID: <1427065530-10695-1-git-send-email-kerolasa@iki.fi> (raw)
Hello,
I noticed a variable shadowing warning, that lead to paying again
attention to dmesg. While recent logger lessons are still fresh in mind
the obvious thing to do with the dmesg was to add more tests, and that's
what this pull is about.
----------------------------------------------------------------
The following changes since commit bb3df8218b4f8f145e345ab59828a9b3d6d70c4b:
tests: some more mount error handling (2015-03-19 17:12:15 +0100)
are available in the git repository at:
git://github.com/kerolasa/lelux-utiliteetit.git test_dmesg
for you to fetch changes up to 29c7d18d92b393c0f87be09bdfee03c93a09e61b:
tests: check dmesg message coloring (2015-03-22 22:56:27 +0000)
----------------------------------------------------------------
Sami Kerola (5):
dmesg: fix shadow declaration
tests: add dmesg multiline message check
tests: add test_dmesg that has fixed boot time
tests: check timestamp formats
tests: check dmesg message coloring
sys-utils/Makemodule.am | 4 ++
sys-utils/dmesg.c | 16 +++---
tests/commands.sh | 2 +-
tests/expected/dmesg/colors | 105 +++++++++++++++++++++++++++++++++++++++
tests/expected/dmesg/indentation | 35 +++++++++++++
tests/ts/dmesg/colors | 25 ++++++++++
tests/ts/dmesg/console-levels | 4 +-
tests/ts/dmesg/decode | 4 +-
tests/ts/dmesg/delta | 4 +-
tests/ts/dmesg/facilities | 4 +-
tests/ts/dmesg/indentation | 37 ++++++++++++++
tests/ts/dmesg/newlines | 5 ++
12 files changed, 228 insertions(+), 17 deletions(-)
create mode 100644 tests/expected/dmesg/colors
create mode 100644 tests/expected/dmesg/indentation
create mode 100755 tests/ts/dmesg/colors
create mode 100755 tests/ts/dmesg/indentation
create mode 100644 tests/ts/dmesg/newlines
--
2.3.3
next reply other threads:[~2015-03-22 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 23:05 Sami Kerola [this message]
2015-03-22 23:05 ` [PATCH 1/5] dmesg: fix shadow declaration Sami Kerola
2015-03-22 23:05 ` [PATCH 2/5] tests: add dmesg multiline message check Sami Kerola
2015-03-22 23:05 ` [PATCH 3/5] tests: add test_dmesg that has fixed boot time Sami Kerola
2015-03-22 23:05 ` [PATCH 4/5] tests: check timestamp formats Sami Kerola
2015-03-22 23:05 ` [PATCH 5/5] tests: check dmesg message coloring Sami Kerola
2015-03-23 10:44 ` [PATCH 0/5] pull: one dmesg compiler warning fix and bunch of tests Karel Zak
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=1427065530-10695-1-git-send-email-kerolasa@iki.fi \
--to=kerolasa@iki.fi \
--cc=util-linux@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