From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: lorenzo@kernel.org, kvalo@codeaurora.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mt76: mt7615: fix mt7615 firmware path definitions" failed to apply to 5.3-stable tree
Date: Thu, 3 Oct 2019 09:54:41 -0400 [thread overview]
Message-ID: <20191003135441.GA17454@sasha-vm> (raw)
In-Reply-To: <157010284795216@kroah.com>
On Thu, Oct 03, 2019 at 01:40:47PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.3-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 9d4d0d06bbf9f7e576b0ebbb2f77672d0fc7f503 Mon Sep 17 00:00:00 2001
>From: Lorenzo Bianconi <lorenzo@kernel.org>
>Date: Sun, 22 Sep 2019 15:36:03 +0200
>Subject: [PATCH] mt76: mt7615: fix mt7615 firmware path definitions
>
>mt7615 patch/n9/cr4 firmwares are available in mediatek folder in
>linux-firmware repository. Because of this mt7615 won't work on regular
>distributions like Ubuntu. Fix path definitions. Moreover remove useless
>firmware name pointers and use definitions directly
>
>Fixes: 04b8e65922f6 ("mt76: add mac80211 driver for MT7615 PCIe-based chipsets")
>Cc: stable@vger.kernel.org
>Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
>Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
I've resolved this by also taking 2fc446487c364 ("mt76: mt7615: always
release sem in mt7615_load_patch"). Queued up both for 5.3 and 5.2, not
needed on older kernels.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-10-03 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 11:40 FAILED: patch "[PATCH] mt76: mt7615: fix mt7615 firmware path definitions" failed to apply to 5.3-stable tree gregkh
2019-10-03 13:54 ` Sasha Levin [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=20191003135441.GA17454@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kvalo@codeaurora.org \
--cc=lorenzo@kernel.org \
--cc=stable@vger.kernel.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.