All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Benjamin Tissoires <btissoir@redhat.com>,
	Peter Hutterer <peter.hutterer@redhat.com>,
	platform-driver-x86@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 0/2] input/serio: Add a firmware_id sysfs attribute
Date: Fri, 28 Mar 2014 09:04:22 -0700	[thread overview]
Message-ID: <20140328160421.GA22658@core.coreip.homeip.net> (raw)
In-Reply-To: <20140328090053.GA10597@srcf.ucam.org>

On Fri, Mar 28, 2014 at 09:00:53AM +0000, Matthew Garrett wrote:
> On Fri, Mar 28, 2014 at 01:52:07AM -0700, Dmitry Torokhov wrote:
> > 
> > Are we even certain that they will be consistent in use of these special
> > PNP ID's? Maybe you should really do DMI match...
> 
> The Windows drivers bind on PNP IDs, not DMI.

OK, fair enough.

-- 
Dmitry

  reply	other threads:[~2014-03-28 16:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 10:12 [PATCH 0/2] input/serio: Add a firmware_id sysfs attribute Hans de Goede
2014-03-20 10:12 ` [PATCH 1/2] " Hans de Goede
2014-03-20 10:12 ` [PATCH 2/2] input/serio/8042: Add firmware_id support Hans de Goede
2014-03-20 17:21 ` [PATCH 0/2] input/serio: Add a firmware_id sysfs attribute Matthew Garrett
2014-03-24  1:07   ` Peter Hutterer
2014-03-28  7:56   ` Dmitry Torokhov
2014-03-28  8:12     ` Hans de Goede
2014-03-28  8:17       ` Dmitry Torokhov
2014-03-28  8:29         ` Hans de Goede
2014-03-28  8:52           ` Dmitry Torokhov
2014-03-28  9:00             ` Matthew Garrett
2014-03-28 16:04               ` Dmitry Torokhov [this message]
2014-03-28  9:05             ` Hans de Goede
2014-03-28  8:20     ` Matthew Garrett
2014-03-28  8:24       ` Dmitry Torokhov
2014-03-28  8:27         ` Matthew Garrett
2014-03-28  8:50           ` Dmitry Torokhov

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=20140328160421.GA22658@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=btissoir@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=peter.hutterer@redhat.com \
    --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 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.