From: J William Piggott <elseifthen@gmx.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: [PATCH 0/3] Pull Request
Date: Tue, 29 Aug 2017 12:30:20 -0400 [thread overview]
Message-ID: <71b98184-ea32-0e83-013c-2fdb8edc621f@gmx.com> (raw)
The following changes since commit e406be01b450dd7ed5e694bc15a39719d6f86967:
hwclock: for debugging print startup system time (2017-08-24 18:49:11 -0400)
are available in the git repository at:
git@github.com:jwpi/util-linux.git 170825
for you to fetch changes up to 0396d0c2bc33a34d132b0d4f9f5f055668732989:
hwclock: close hwaudit_fd unconditionally (2017-08-28 21:19:55 -0400)
----------------------------------------------------------------
J William Piggott (3):
hwclock: remove sysexits.h
hwclock: remove audit from control struct
hwclock: close hwaudit_fd unconditionally
sys-utils/hwclock-rtc.c | 5 +--
sys-utils/hwclock.8.in | 8 ++++
sys-utils/hwclock.c | 104 +++++++++++++++++++-----------------------------
sys-utils/hwclock.h | 3 +-
4 files changed, 52 insertions(+), 68 deletions(-)
next reply other threads:[~2017-08-29 16:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 16:30 J William Piggott [this message]
2017-08-29 16:33 ` [PATCH 1/3] hwclock: remove sysexits.h J William Piggott
2017-08-29 16:34 ` [PATCH 2/3] hwclock: remove audit from control struct J William Piggott
2017-08-30 7:40 ` Karel Zak
2017-08-30 17:56 ` J William Piggott
2017-09-03 19:59 ` J William Piggott
2017-09-03 21:54 ` Sami Kerola
2017-09-04 1:22 ` J William Piggott
2017-09-03 20:01 ` [v2 PATCH 2/3] hwclock: don't always use hwclock_exit J William Piggott
2017-08-29 16:35 ` [PATCH 3/3] hwclock: close hwaudit_fd unconditionally J William Piggott
2017-09-05 10:27 ` [PATCH 0/3] Pull Request 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=71b98184-ea32-0e83-013c-2fdb8edc621f@gmx.com \
--to=elseifthen@gmx.com \
--cc=kzak@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).