From: Karel Zak <kzak@redhat.com>
To: Sami Kerola <kerolasa@iki.fi>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 2/3] logindefs: remove unused function
Date: Tue, 28 Nov 2017 14:52:26 +0100 [thread overview]
Message-ID: <20171128135226.o2ugb7qwnk4dbyzd@ws.net.home> (raw)
In-Reply-To: <20171126174751.10500-2-kerolasa@iki.fi>
On Sun, Nov 26, 2017 at 05:47:50PM +0000, Sami Kerola wrote:
> login-utils/logindefs.c | 18 ------------------
> login-utils/logindefs.h | 1 -
> 2 files changed, 19 deletions(-)
All patches applied except this patch.
I've added free_getlogindefs_data() to su(1) and login(1). It seems
like a good idea to deallocate the config file when we only wait for
child process.
Thanks!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2017-11-28 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 17:47 [PATCH 1/3] lib/signames: remove unused function Sami Kerola
2017-11-26 17:47 ` [PATCH 2/3] logindefs: " Sami Kerola
2017-11-28 13:52 ` Karel Zak [this message]
2017-11-26 17:47 ` [PATCH 3/3] eject: remove list_speeds() #ifdef CDROM_SELECT_SPEED protection Sami Kerola
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=20171128135226.o2ugb7qwnk4dbyzd@ws.net.home \
--to=kzak@redhat.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).