From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Benjamin Tissoires <btissoir@redhat.com>,
Peter Hutterer <peter.hutterer@redhat.com>,
linux-input@vger.kernel.org
Subject: [PATCH v3 0/2] input/serio: Add a firmware_id sysfs attribute
Date: Mon, 14 Apr 2014 12:30:17 +0200 [thread overview]
Message-ID: <1397471419-31224-1-git-send-email-hdegoede@redhat.com> (raw)
Hi All,
Here is v3 of my serio firmware_id sysfs attribute patch-set
Changes in v2:
-Add a helper function to avoid copy/pasting the code for building
the firmware_id string from pnp_ids
Changes in v3:
-Prefix the firmware_id string for 8042-pnp devices which "PNP: " so that
it will be easy to differentiate pnp-ids from ie devicetree ids in the future
Regards,
Hans
next reply other threads:[~2014-04-14 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 10:30 Hans de Goede [this message]
2014-04-14 10:30 ` [PATCH v3 1/2] input/serio: Add a firmware_id sysfs attribute Hans de Goede
2014-04-14 10:34 ` [PATCH v3 2/2] input/serio/8042: Add firmware_id support Hans de Goede
2014-04-20 5:31 ` [PATCH v3 0/2] input/serio: Add a firmware_id sysfs attribute 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=1397471419-31224-1-git-send-email-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=btissoir@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@redhat.com \
/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).