public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Steve Muckle <smuckle@google.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/ustat: convert to new lib, use direct syscall
Date: Fri, 1 Feb 2019 16:19:07 -0800	[thread overview]
Message-ID: <5468c7b4-0236-2637-9bac-e207dfe97e5b@google.com> (raw)
In-Reply-To: <20190130104007.GA32120@rei>

On 01/30/2019 02:40 AM, Cyril Hrubis wrote:
> Hi!
>>> +++ b/include/lapi/ustat.h
>>> @@ -0,0 +1,8 @@
>>> +#include <sys/types.h>
>> I'd put here at least
>> //SPDX-License-Identifier: GPL-2.0-or-later
>>> +
>>> +struct ustat {
>>> +	daddr_t f_tfree;
>>> +	ino_t f_tinode;
>>> +	char f_fname[6];
>>> +	char f_fpack[6];
>>> +};
>> Thinking about it twice, wouldn't be better to include <sys/ustat.h> and detect
>> with autotools whether struct ustat is defined and use this only if it's not
>> defined? The same approach we use for struct statx?
> 
> And we do have the configure check for ustat.h in place so this should
> be as easy as doing:
> 
> #ifdef HAVE_SYS_USTAT_H
> # include <sys/ustat.h>
> #else
> struct ustat {
> ...
> }
> #endif
> 
> Also ideally this header should include guards, even if it's unlikely to
> be included twice.
> 
>>> +++ b/testcases/kernel/syscalls/ustat/ustat01.c
>>> @@ -1,21 +1,7 @@
>>> +// SPDX-License-Identifier: GPL-2.0
>> @Cyril: can we use GPL-2.0-or-later? Original was GPL only.
> 
> I would have kept it GPL-2.0 unless it's rewritten from scratch
> completely.

Thanks Petr and Cyril for the review, v2 sent.

      reply	other threads:[~2019-02-02  0:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29  2:37 [LTP] [PATCH] syscalls/ustat: convert to new lib, use direct syscall Steve Muckle
2019-01-29 17:55 ` Petr Vorel
2019-01-29 18:06 ` Petr Vorel
2019-01-30 10:40   ` Cyril Hrubis
2019-02-02  0:19     ` Steve Muckle [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=5468c7b4-0236-2637-9bac-e207dfe97e5b@google.com \
    --to=smuckle@google.com \
    --cc=ltp@lists.linux.it \
    /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