From: Kalle Valo <kvalo@codeaurora.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [fix?] bcma: use (get|put)_device when probing/removing device driver
Date: Tue, 31 Jan 2017 07:15:26 +0000 (UTC) [thread overview]
Message-ID: <20170131071526.C93CA6072E@smtp.codeaurora.org> (raw)
In-Reply-To: <20170128133122.12360-1-zajec5@gmail.com>
Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> This allows tracking device state and e.g. makes devm work as expected.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> Cc: Stable <stable@vger.kernel.org>
At this stage of the cycle I think 4.11 is more approriate for this fix.
--
https://patchwork.kernel.org/patch/9543283/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-01-31 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 13:31 [PATCH fix?] bcma: use (get|put)_device when probing/removing device driver Rafał Miłecki
2017-01-31 7:15 ` Kalle Valo [this message]
2017-01-31 7:27 ` [fix?] " Kalle Valo
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=20170131071526.C93CA6072E@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=zajec5@gmail.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).