From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Iván Ezequiel Rodriguez" <ivanrwcm25@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Input: evdev: propagate EVIOCSFF copy errors correctly
Date: Tue, 27 Oct 2026 11:41:24 -0700 [thread overview]
Message-ID: <auDwT-N9DzZZ9BJo@google.com> (raw)
In-Reply-To: <20260831192752.258550-2-ivanrwcm25@gmail.com>
On Mon, Aug 31, 2026 at 04:27:51PM -0300, Iván Ezequiel Rodriguez wrote:
> Return the error from input_ff_effect_from_user() instead of always
> mapping failures to -EFAULT, so wrong buffer sizes surface as -EINVAL.
>
> Signed-off-by: Iván Ezequiel Rodriguez <ivanrwcm25@gmail.com>
Applied, thank you.
--
Dmitry
next prev parent reply other threads:[~2026-10-27 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 15:21 [PATCH v1 0/2] Input: evdev/uinput errno alignment Iván Ezequiel Rodriguez
2026-08-31 15:21 ` [PATCH v1 1/2] Input: evdev: propagate EVIOCSFF copy errors correctly Iván Ezequiel Rodriguez
2026-08-31 18:30 ` sashiko-bot
2026-08-31 15:21 ` [PATCH v1 2/2] Input: uinput: align UI_ABS_SETUP validation with uapi docs Iván Ezequiel Rodriguez
2026-08-31 18:42 ` sashiko-bot
2026-08-31 19:27 ` [PATCH v2 0/2] Input: evdev/uinput errno alignment Iván Ezequiel Rodriguez
2026-08-31 19:27 ` [PATCH v2 1/2] Input: evdev: propagate EVIOCSFF copy errors correctly Iván Ezequiel Rodriguez
2026-08-31 21:35 ` sashiko-bot
2026-10-27 18:41 ` Dmitry Torokhov [this message]
2026-08-31 19:27 ` [PATCH v2 2/2] Input: uinput: return -EINVAL for out-of-range UI_ABS_SETUP axis code Iván Ezequiel Rodriguez
2026-10-27 18:40 ` Dmitry Torokhov
2026-10-28 15:03 ` [PATCH] Input: uinput: document -ERANGE for UI_ABS_SETUP axis codes Iván Ezequiel Rodriguez
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=auDwT-N9DzZZ9BJo@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=ivanrwcm25@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.