From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: John Stultz <john.stultz@linaro.org>,
Marcel Holtmann <marcel@holtmann.org>,
Rob Herring <rob.herring@linaro.org>,
Johan Hovold <johan@kernel.org>,
Ronald Tschalaer <ronald@innovation.ch>,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Backport d73e17281665 to v4.15 stable
Date: Thu, 1 Feb 2018 07:42:30 +0100 [thread overview]
Message-ID: <20180201064230.GA15417@kroah.com> (raw)
In-Reply-To: <20180201055052.GA19082@wunner.de>
On Thu, Feb 01, 2018 at 06:50:52AM +0100, Lukas Wunner wrote:
> Dear Greg,
>
> when you refill the patch queue for v4.15 stable one of these days,
> please consider adding
>
> commit d73e172816652772114827abaa2dbc053eecbbd7
> Author: Lukas Wunner <lukas@wunner.de>
> Date: Fri Nov 17 00:54:53 2017 +0100
>
> Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops
>
> to fix a boot crash on certain machines with UART-attached Bluetooth
> which was kindly reported by John Stultz. The patch unfortunately
> lacked a Fixes: or Cc: stable tag. It landed in Linus' tree 7 hours ago.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2018-02-01 6:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 2:00 Boot crash @hci_uart_tx_wakeup+0x38/0x148 w/ Linus' HEAD? John Stultz
2017-11-16 20:58 ` John Stultz
2017-11-16 21:30 ` Lukas Wunner
2017-11-16 21:45 ` Lukas Wunner
2017-11-16 22:29 ` John Stultz
2017-11-16 23:54 ` [PATCH] Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops Lukas Wunner
2017-11-16 23:59 ` Lukas Wunner
2017-11-17 6:07 ` Marcel Holtmann
2017-12-11 21:49 ` John Stultz
2018-01-02 20:39 ` John Stultz
2018-01-02 20:45 ` Marcel Holtmann
2018-02-01 5:50 ` Backport d73e17281665 to v4.15 stable Lukas Wunner
2018-02-01 6:42 ` Greg Kroah-Hartman [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=20180201064230.GA15417@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=marcel@holtmann.org \
--cc=rob.herring@linaro.org \
--cc=ronald@innovation.ch \
--cc=sumit.semwal@linaro.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.