From: Karel Zak <kzak@redhat.com>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
util-linux@vger.kernel.org, Masatake YAMATO <yamato@redhat.com>
Subject: Re: [PATCH v3] flock: add support for using fcntl() with open file description locks
Date: Mon, 29 Apr 2024 10:29:28 +0200 [thread overview]
Message-ID: <20240429082928.cuodskfd5kqljf7l@ws.net.home> (raw)
In-Reply-To: <a0de91f6-2eb0-4526-a50a-b89db9fe140f@t-8ch.de>
On Sun, Apr 28, 2024 at 11:07:56PM +0200, Thomas Weißschuh wrote:
> >
> > sys-utils/flock.c | 78 +++++++++++++++++++++++++++++++++++++++++++++--
>
> Some testcases in tests/ts/misc/flock would be nice.
+1
Merged, for tests use another PR.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2024-04-29 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 9:44 [PATCH v3] flock: add support for using fcntl() with open file description locks Rasmus Villemoes
2024-04-26 8:01 ` Karel Zak
2024-04-28 21:07 ` Thomas Weißschuh
2024-04-29 8:29 ` Karel Zak [this message]
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=20240429082928.cuodskfd5kqljf7l@ws.net.home \
--to=kzak@redhat.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=thomas@t-8ch.de \
--cc=util-linux@vger.kernel.org \
--cc=yamato@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).