From: jeffy <jeffy.chen@rock-chips•com>
To: Rohit Vaswani <rvaswani@nvidia•com>,
"linux-bluetooth@vger•kernel.org"
<linux-bluetooth@vger•kernel.org>
Cc: Brian Norris <briannorris@chromium•org>,
Douglas Anderson <dianders@chromium•org>,
Johan Hedberg <johan.hedberg@intel•com>,
Peter Hurley <peter@hurleysoftware•com>,
Johan Hedberg <johan.hedberg@gmail•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"David S. Miller" <davem@davemloft•net>,
Marcel Holtmann <marcel@holtmann•org>,
Gustavo Padovan <gustavo@padovan•org>
Subject: Re: Bluetooth: might sleep error in hidp_session_thread
Date: Fri, 23 Jun 2017 20:38:54 +0800 [thread overview]
Message-ID: <594D0BDE.10102@rock-chips.com> (raw)
In-Reply-To: <7be134d7f9904082a35a9cc926ec24d3@HQMAIL106.nvidia.com>
Hi Rohit,
Thanx for your reply, and sorry to the delay, somehow your mail was
marked as spam by the mail server :(
On 06/13/2017 02:31 AM, Rohit Vaswani wrote:
> Hi Jeffy,
>
> I was looking into the patch from Jeffy Chen from February 14 2017 :
> [v4,3/3] Bluetooth: hidp: fix possible might sleep error in hidp_session_thread: https://patchwork.kernel.org/patch/9570931/
>
> We faced a similar issue and this patch seems to fix the problem in our preliminary test.
> I am trying to check if there was a reason this wasn't merged earlier ?
hmm, i'm not sure why, but please feel free to add your test-by~
>
> Thanks,
> Rohit
>
> nvpublic
>
>
>
next prev parent reply other threads:[~2017-06-23 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 18:31 Bluetooth: might sleep error in hidp_session_thread Rohit Vaswani
2017-06-23 12:38 ` jeffy [this message]
2017-06-23 18:00 ` Rohit Vaswani
[not found] ` <cc75d14021724c2d8b74a92482d67b7b-wO81nVYWzR5AOoK4uxnQ11aTQe2KTcn/@public.gmane.org>
2017-06-27 9:43 ` jeffy
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=594D0BDE.10102@rock-chips.com \
--to=jeffy.chen@rock-chips$(echo .)com \
--cc=briannorris@chromium$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dianders@chromium$(echo .)org \
--cc=gustavo@padovan$(echo .)org \
--cc=johan.hedberg@gmail$(echo .)com \
--cc=johan.hedberg@intel$(echo .)com \
--cc=linux-bluetooth@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=marcel@holtmann$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=peter@hurleysoftware$(echo .)com \
--cc=rvaswani@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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