From: Tim Niemeyer <tim.niemeyer@mastersword.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Tim Niemeyer <tim.niemeyer@corscience.de>,
Felipe Balbi <balbi@ti.com>,
stable@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
jslaby@suse.cz, grant.likely@linaro.org,
linux-bluetooth@vger.kernel.org, andreas@biessmann.de
Subject: Re: [PATCH] bluetooth: hci_ldisc: fix deadlock condition
Date: Sat, 23 Aug 2014 11:50:26 +0200 [thread overview]
Message-ID: <1408787426.28950.41.camel@redi7> (raw)
In-Reply-To: <20140822155140.GA18880@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
Hi
Am Freitag, den 22.08.2014, 10:51 -0500 schrieb Greg KH:
> On Fri, Aug 22, 2014 at 03:45:07PM +0200, Tim Niemeyer wrote:
> > This Patch was applied to 3.10 and 3.2. It's probably missed on 3.4.
>
> Does it apply there?
The original patch applies not cleanly on 3.4. The init_work is not
available there.
I backported it and it's the same result as the backport from Andreas.
He tested the patch on 3.4.87. The attached patch of my last mail
applies.
> What is the git id of the commit?
Sorry, missed it:
commit da64c27d3c93ee9f89956b9de86c4127eb244494 upstream
commit a22d29e6e5757b1daed7d0b409a815eb33f66e4e stable-3.10
commit 87520218746b8d973670e37237666f174590898c stable-3.2
Tim
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-08-23 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398265117-11793-2-git-send-email-balbi@ti.com>
2014-08-22 13:45 ` [PATCH] bluetooth: hci_ldisc: fix deadlock condition Tim Niemeyer
2014-08-22 15:51 ` Greg KH
2014-08-23 9:50 ` Tim Niemeyer [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=1408787426.28950.41.camel@redi7 \
--to=tim.niemeyer@mastersword.de \
--cc=andreas@biessmann.de \
--cc=balbi@ti.com \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.org \
--cc=tim.niemeyer@corscience.de \
/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