From: Kalle Valo <kalle.valo@canonical.com>
To: ofono@ofono.org
Subject: commit "Fix Use hashtable to record udev path" breaks huawei
Date: Wed, 19 May 2010 16:19:56 +0300 [thread overview]
Message-ID: <87tyq46nb7.fsf@potku.valot.fi> (raw)
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
Hi,
while working on third version of my huawei gprs patches I noticed that
this commit breaks huawei:
commit af976f7e524746b1b55645967e11ab8250f593a8
Author: Zhenhua Zhang <zhenhua.zhang@intel.com>
Date: Tue May 11 09:04:28 2010 +0800
Fix Use hashtable to record udev path
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.
I reverted the commit and huawei works again for me. More details later
today.
--
Kalle Valo
next reply other threads:[~2010-05-19 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 13:19 Kalle Valo [this message]
2010-05-19 15:23 ` commit "Fix Use hashtable to record udev path" breaks huawei Kalle Valo
2010-05-19 13:55 ` Denis Kenzior
2010-05-20 1:18 ` Zhang, Zhenhua
2010-05-20 5:13 ` Kalle Valo
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=87tyq46nb7.fsf@potku.valot.fi \
--to=kalle.valo@canonical.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 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.