mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: dmitry.torokhov@gmail.com, o2g.org.ru@gmail.com,
	 Armin Wolf <W_Armin@gmx.de>
Cc: hdegoede@redhat.com, corentin.chary@gmail.com, luke@ljones.dev,
	 mjg59@srcf.ucam.org, pali@kernel.org,
	eric.piel@tremplin-utc.net,  jlee@suse.com,
	kenneth.t.chan@gmail.com, coproscefalo@gmail.com,
	 linux-input@vger.kernel.org,
	platform-driver-x86@vger.kernel.org,
	 linux-kernel@vger.kernel.org, josh@joshuagrisham.com
Subject: Re: [PATCH v3] Input: i8042 - Add support for platform filter contexts
Date: Tue, 14 Jan 2025 17:48:59 +0200	[thread overview]
Message-ID: <173686973958.7065.12791132870545458476.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250113221314.435812-1-W_Armin@gmx.de>

On Mon, 13 Jan 2025 23:13:14 +0100, Armin Wolf wrote:

> Currently the platform filter cannot access any driver-specific state
> which forces drivers installing a i8042 filter to have at least some
> kind of global pointer for their filter.
> 
> Allow callers of i8042_install_filter() to submit a context pointer
> which is then passed to the i8042 filter. This frees drivers from the
> responsibility of having to manage this global pointer themself.
> 
> [...]


Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.

The list of commits applied:
[1/1] Input: i8042 - Add support for platform filter contexts
      commit: 08cd46acfc4fc6d810433f35dbc1dab6e1a6891b

--
 i.


      reply	other threads:[~2025-01-14 15:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13 22:13 Armin Wolf
2025-01-14 15:48 ` Ilpo Järvinen [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=173686973958.7065.12791132870545458476.b4-ty@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=W_Armin@gmx.de \
    --cc=coproscefalo@gmail.com \
    --cc=corentin.chary@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eric.piel@tremplin-utc.net \
    --cc=hdegoede@redhat.com \
    --cc=jlee@suse.com \
    --cc=josh@joshuagrisham.com \
    --cc=kenneth.t.chan@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=mjg59@srcf.ucam.org \
    --cc=o2g.org.ru@gmail.com \
    --cc=pali@kernel.org \
    --cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®