From: macmpi <spam@ipik.org>
To: Jiri Kosina <jikos@jikos.cz>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
dmitry.torokhov@gmail.com
Cc: andrew.smirnov@gmail.com, enric.balletbo@collabora.com,
kirr@nexedi.com, linux-bluetooth@vger.kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
logang@deltatee.com, luiz.dentz@gmail.com, pali.rohar@gmail.com,
tglx@linutronix.de, abhishekpandit@chromium.org
Subject: Re: [PATCH] Input: uinput - Add UI_SET_UNIQ ioctl handler
Date: Wed, 29 Jun 2022 11:31:16 +0200 [thread overview]
Message-ID: <ddc4f559-f03c-8d40-73a7-93d767b45bd6@ipik.org> (raw)
In-Reply-To: <20191127185139.65048-1-abhishekpandit@chromium.org>
Hi!
Bug 216134 has been been submitted on this issue
https://bugzilla.kernel.org/show_bug.cgi?id=216134
Thanks for consideration and feedback.
prev parent reply other threads:[~2022-06-29 9:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 18:51 [PATCH] Input: uinput - Add UI_SET_UNIQ ioctl handler Abhishek Pandit-Subedi
2019-12-01 14:53 ` Pali Rohár
2019-12-02 1:23 ` Dmitry Torokhov
2019-12-02 8:47 ` Pali Rohár
2019-12-02 17:54 ` Dmitry Torokhov
2019-12-02 18:53 ` Pali Rohár
2019-12-02 19:36 ` Dmitry Torokhov
2019-12-02 22:54 ` Abhishek Pandit-Subedi
2019-12-02 23:09 ` Pali Rohár
2019-12-03 17:38 ` Pali Rohár
2019-12-03 19:11 ` Dmitry Torokhov
2019-12-04 12:02 ` Luiz Augusto von Dentz
2019-12-04 21:59 ` Abhishek Pandit-Subedi
2019-12-05 10:52 ` Pali Rohár
2019-12-05 20:03 ` Abhishek Pandit-Subedi
2019-12-06 9:11 ` Pali Rohár
2019-12-06 17:40 ` Dmitry Torokhov
2019-12-16 21:57 ` Abhishek Pandit-Subedi
2019-12-18 11:02 ` Pali Rohár
2019-12-18 11:26 ` Pali Rohár
2020-03-22 15:47 ` Pali Rohár
2022-06-13 21:36 ` Luiz Augusto von Dentz
2024-02-06 17:17 ` Chris Morgan
2024-02-06 17:44 ` Pali Rohár
2019-12-04 1:49 ` Marcel Holtmann
2022-06-29 9:31 ` macmpi [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=ddc4f559-f03c-8d40-73a7-93d767b45bd6@ipik.org \
--to=spam@ipik.org \
--cc=abhishekpandit@chromium.org \
--cc=andrew.smirnov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=jikos@jikos.cz \
--cc=kirr@nexedi.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=luiz.dentz@gmail.com \
--cc=pali.rohar@gmail.com \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).