From: Vignesh Raghavendra <vigneshr@ti.com>
To: Merlijn Wajer <merlijn@wizzup.org>,
"kvalo@codeaurora.org" <kvalo@codeaurora.org>
Cc: linux-omap <linux-omap@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Sebastian Reichel <sre@kernel.org>, Pavel Machek <pavel@ucw.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"broonie@kernel.org" <broonie@kernel.org>
Subject: Re: Nokia N900: wl1251 spi3.0: EOW timed out on
Date: Mon, 11 Mar 2019 12:51:57 +0530 [thread overview]
Message-ID: <ddfababf-3d3c-85c1-e1d8-762b4c41f19c@ti.com> (raw)
In-Reply-To: <1b2918b4-1765-5aba-4752-1d04bdfea925@wizzup.org>
On 11/03/19 12:53 AM, Merlijn Wajer wrote:
> Hi,
>
> On 10/03/2019 05:16, Vignesh Raghavendra wrote:
>> Hi.
>>
>> On 10-Mar-19 6:23 AM, Merlijn Wajer wrote:
>>>
>>> Hi,
>>>
>>> On 10/03/2019 00:22, Merlijn Wajer wrote:
>>>> Hi,
>>>>
>>>> I just migrated to Linux 5.0 (from 4.15) on my Nokia N900, and I'm
>>>> getting a lot of messages like this:
>>>>
>>>>> wl1251 spi3.0: EOW timed out
>>
>>
>> Could you try if this patch fixes the issue? This is part of latest mainline tree but not part of 5.0:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=baf8b9f8d260c55a86405f70a384c29cda888476
>
> This seems to fix the issue. Would it make sense to queue this for an
> upcoming fixes release for 5.0?
>
Patch carries "Cc: stable@vger.kernel.org" tag. So, will be backported
to stable trees. It will be part of one of 5.0.y stable releases.
> Cheers,
> Merlijn
>
--
Regards
Vignesh
prev parent reply other threads:[~2019-03-11 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 23:22 Nokia N900: wl1251 spi3.0: EOW timed out on Merlijn Wajer
2019-03-10 0:53 ` Merlijn Wajer
2019-03-10 4:16 ` Vignesh Raghavendra
2019-03-10 19:23 ` Merlijn Wajer
2019-03-11 7:21 ` Vignesh Raghavendra [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=ddfababf-3d3c-85c1-e1d8-762b4c41f19c@ti.com \
--to=vigneshr@ti.com \
--cc=broonie@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=tony@atomide.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).