From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>, Len Brown <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [PATCH 0/2] PNPACPI: cope with invalid device IDs
Date: Fri, 04 Jun 2010 19:23:59 -0700 [thread overview]
Message-ID: <20100605022058.25768.77560.stgit@localhost.localdomain> (raw)
Bjorn, Len,
Here is the updated version of the patch that handles invalid _HIDs,
this time without adding duplicate entriess into the ID list. There
is also a second patch adding error handling into pnp_add_device().
Please consider applying.
Thank you,
--
Dmitry
next reply other threads:[~2010-06-05 2:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 2:23 Dmitry Torokhov [this message]
2010-06-05 2:24 ` [PATCH 1/2] PNPACPI: cope with invalid device IDs Dmitry Torokhov
2010-09-17 22:37 ` Bjorn Helgaas
2010-09-17 22:49 ` Dmitry Torokhov
2010-09-17 22:56 ` Bjorn Helgaas
2010-09-18 17:11 ` Dmitry Torokhov
2010-10-01 6:09 ` Len Brown
2010-06-05 2:24 ` [PATCH 2/2] PNPACPI: check return value of pnp_add_device() 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=20100605022058.25768.77560.stgit@localhost.localdomain \
--to=dmitry.torokhov@gmail.com \
--cc=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@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 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).