From: Johan Hedberg <johan.hedberg@gmail.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Chan-yeol Park <chanyeol.park@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2014-11-07
Date: Wed, 19 Nov 2014 13:17:44 +0200 [thread overview]
Message-ID: <20141119111744.GA8153@t440s.lan> (raw)
In-Reply-To: <20141119110654.GA1894@node.dhcp.inet.fi>
Hi Kirill,
On Wed, Nov 19, 2014, Kirill A. Shutemov wrote:
> > From: Johan Hedberg <johan.hedberg@intel.com>
> > Date: Tue, 18 Nov 2014 20:00:15 +0200
> > Subject: [PATCH] Bluetooth: Fix setting state back to TASK_RUNNING
> >
> > In __hci_cmd_sync_ev() and __hci_req_sync() if the hci_req_run() call
> > fails and we return from the functions we should ensure that the state
> > doesn't remain in TASK_INTERRUPTIBLE that we just set it to. This patch
> > fixes missing calls to set_current_state(TASK_RUNNING) in both places.
> >
> > Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
>
> This patch helps -- warning is gone.
Thanks! I've resent it to linux-bluetooth with the appropriate
Reported-by/Tested-by credits. It'll be included in the next pull
request for the bluetooth-next tree.
Johan
prev parent reply other threads:[~2014-11-19 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 9:27 pull request: bluetooth-next 2014-11-07 Johan Hedberg
2014-11-11 21:35 ` John W. Linville
2014-11-18 13:34 ` Kirill A. Shutemov
2014-11-18 18:09 ` Johan Hedberg
2014-11-19 8:18 ` Chan-yeol Park
2014-11-19 8:20 ` Chan-yeol Park
2014-11-19 11:06 ` Kirill A. Shutemov
2014-11-19 11:17 ` Johan Hedberg [this message]
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=20141119111744.GA8153@t440s.lan \
--to=johan.hedberg@gmail.com \
--cc=chanyeol.park@samsung.com \
--cc=kirill@shutemov.name \
--cc=kyungmin.park@samsung.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).