All of lore.kernel.org
 help / color / mirror / Atom feed
From: Werner Sembach <wse@tuxedocomputers.com>
To: dmitry.torokhov@gmail.com, tiwai@suse.de, mpdesouza@suse.com,
	arnd@arndb.de, hdegoede@redhat.com, samuel@cavoj.net,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] input/i8042: Rework quirk tables
Date: Tue, 28 Jun 2022 16:15:20 +0200	[thread overview]
Message-ID: <c9eae62f-7220-a7f0-635e-e9880d49b218@tuxedocomputers.com> (raw)
In-Reply-To: <20220329143622.31394-1-wse@tuxedocomputers.com>

On 3/29/22 16:36, Werner Sembach wrote:
> Revision 5 with some fixes based on feedback by Hans de Goede.
>
> The 1st patch is minor housekeeping.
>
> The 2nd patch merges the tables together. Minor fixes in 5th revision and
> no more duplication of ASUS devices
>
> The 3rd patch add optional debug output to see which quirks get applied. In
> 5th revision this no longer breaks compilation on non x86 platforms.
>
> The 4th patch adds a list of Clevo devices that need multiple quirks.
> With the reworked table they don't need to be inserted multiple times now,
> which was required in v1 and v2 of this patch.
>
> I also included the extra quirk for the Clevo NS7xMU, which was a separate
> patch before.
>
> The added Clevo devices are now only identified by their board name as this
> is the only somewhat reliable string that might not be changed by resellers.
>
>
Just a friendly reminder. Is there any update on this?

Kind regards,

Werner Sembach


      parent reply	other threads:[~2022-06-28 14:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 14:36 [PATCH v5] input/i8042: Rework quirk tables Werner Sembach
2022-03-29 14:36 ` [PATCH v5 1/4] input/i8042: Move __initconst to fix code styling warning Werner Sembach
2022-03-29 14:36 ` [PATCH v5 2/4] input/i8042: Merge quirk tables Werner Sembach
2022-03-29 14:36 ` [PATCH v5 3/4] input/i8042: Add debug output for quirks Werner Sembach
2022-03-29 14:36 ` [PATCH v5 4/4] input/i8042: Add TUXEDO devices to i8042 quirk tables Werner Sembach
2022-06-29  5:36   ` Dmitry Torokhov
2022-06-29 11:29     ` Werner Sembach
2022-03-29 14:41 ` [PATCH v5] input/i8042: Rework " Werner Sembach
2022-04-02 10:47 ` Hans de Goede
2022-04-04 14:36   ` Werner Sembach
2022-06-28 14:15 ` Werner Sembach [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=c9eae62f-7220-a7f0-635e-e9880d49b218@tuxedocomputers.com \
    --to=wse@tuxedocomputers.com \
    --cc=arnd@arndb.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpdesouza@suse.com \
    --cc=samuel@cavoj.net \
    --cc=tiwai@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 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.