From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/2] lapi: Add uinput.h
Date: Wed, 25 Oct 2023 09:39:52 +0200 [thread overview]
Message-ID: <20231025073952.GA286089@pevik> (raw)
In-Reply-To: <8734xzuq4g.fsf@suse.de>
Hi Richie,
> > +++ b/configure.ac
> > @@ -67,6 +67,7 @@ AC_CHECK_HEADERS_ONCE([ \
> > linux/tls.h \
> > linux/tty.h \
> > linux/types.h \
> > + linux/uinput.h \
> Do we use this?
Yes, see below.
> > linux/userfaultfd.h \
> > netinet/sctp.h \
> > pthread.h \
> > diff --git a/include/lapi/uinput.h b/include/lapi/uinput.h
> > new file mode 100644
> > index 000000000..bdd6f466f
> > --- /dev/null
> > +++ b/include/lapi/uinput.h
> > @@ -0,0 +1,15 @@
> > +// SPDX-License-Identifier: GPL-2.0-or-later
> > +/*
> > + * Copyright (c) 2023 Petr Vorel <pvorel@suse.cz>
> > + */
> > +
> > +#ifndef LAPI_UINPUT_H__
> > +#define LAPI_UINPUT_H__
> > +
> > +#include <linux/uinput.h>
Here. We have policy, that we first load the header and then check for a
fallback.
Kind regards,
Petr
> > +
> > +#ifndef UI_GET_SYSNAME
> > +# define UI_GET_SYSNAME(len) _IOC(_IOC_READ, UINPUT_IOCTL_BASE, 44, len)
> > +#endif
> > +
> > +#endif /* LAPI_UINPUT_H__ */
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-10-25 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 20:11 [LTP] [PATCH 0/2] Fix CI for CentOS 7 Petr Vorel
2023-10-24 20:11 ` [LTP] [PATCH 1/2] lapi: Add uinput.h Petr Vorel
2023-10-25 7:18 ` Richard Palethorpe
2023-10-25 7:39 ` Petr Vorel [this message]
2023-10-25 7:51 ` Cyril Hrubis
2023-10-25 8:12 ` Petr Vorel
2023-10-25 8:14 ` Cyril Hrubis
2023-10-25 8:22 ` Petr Vorel
2023-10-25 7:52 ` Richard Palethorpe
2023-10-24 20:11 ` [LTP] [PATCH 2/2] input_helper: Fix compilation on CentOS 7 Petr Vorel
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=20231025073952.GA286089@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.de \
/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