From: Hayes Wang <hayeswang@realtek.com>
To: Hayes Wang <hayeswang@realtek.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: nic_swsd <nic_swsd@realtek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: [PATCH net-next] r8152: add rtnl_lock
Date: Thu, 9 Oct 2014 07:59:35 +0000 [thread overview]
Message-ID: <0835B3720019904CB8F7AA43166CEEB2EC397E@RTITMBSTEMP01.realtek.com.tw> (raw)
In-Reply-To: <1394712342-15778-59-Taiwan-albertk@realtek.com>
> -----Original Message-----
> From: Hayes Wang
> Sent: Thursday, October 09, 2014 2:25 PM
> To: netdev@vger.kernel.org
> Cc: nic_swsd; linux-kernel@vger.kernel.org;
> linux-usb@vger.kernel.org; Hayes Wang
> Subject: [PATCH net-next] r8152: add rtnl_lock
>
> Add rtnl_lock() for suspend/resume and workqueue.
>
> Signed-off-by: Hayes Wang <hayeswang@realtek.com>
Excuse me. The patch has the dead lock issue when
enabling autosuspend. Please ignore this patch.
Best Regards,
Hayes
next prev parent reply other threads:[~2014-10-09 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 5:36 [PATCH net-next] r8152: use mutex for hw settings Hayes Wang
2014-10-08 19:45 ` David Miller
2014-10-09 7:59 ` Hayes Wang
2014-10-09 23:05 ` David Miller
2014-10-09 6:24 ` [PATCH net-next] r8152: add rtnl_lock Hayes Wang
2014-10-09 7:59 ` Hayes Wang [this message]
2014-10-09 10:00 ` [PATCH net-next v2 0/3] r8152: use mutex for hw settings Hayes Wang
2014-10-09 10:00 ` [PATCH net-next v2 1/3] r8152: autoresume before setting feature Hayes Wang
2014-10-09 10:00 ` [PATCH net-next v2 2/3] r8152: adjust usb_autopm_xxx Hayes Wang
2014-10-09 10:00 ` [PATCH net-next v2 3/3] r8152: add mutex for hw settings Hayes Wang
2014-10-09 23:06 ` [PATCH net-next v2 0/3] r8152: use " David Miller
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=0835B3720019904CB8F7AA43166CEEB2EC397E@RTITMBSTEMP01.realtek.com.tw \
--to=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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
all inboxes | Powered by JetHome®