From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/2] Fix Use hashtable to record udev path
Date: Tue, 11 May 2010 09:21:10 -0500 [thread overview]
Message-ID: <201005110921.10985.denkenz@gmail.com> (raw)
In-Reply-To: <1273539869-23803-1-git-send-email-zhenhua.zhang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
Hi Zhenhua,
> Sometimes, Udev device 'remove' event could not report correct parent
> node of current udev_device. Current code replies on the devpath
> attached on the parent node to find modem and then remove it.
>
> This fix is to change the way to store the devpath info into a
> hashtable. So that we search hashtable to get devpath and remove the
> modem.
Patch has been applied, thanks.
Regards,
-Denis
next prev parent reply other threads:[~2010-05-11 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 1:04 [PATCH 1/2] Fix Use hashtable to record udev path Zhenhua Zhang
2010-05-11 1:04 ` [PATCH 2/2] Fix update driver attached status by CGREG notify Zhenhua Zhang
2010-05-11 14:21 ` Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-06 6:28 [PATCH 1/2] Fix Use hashtable to record udev path Zhenhua Zhang
2010-05-06 6:30 ` Zhang, Zhenhua
2010-05-10 14:33 ` Denis Kenzior
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=201005110921.10985.denkenz@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.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