From: Kalle Valo <kvalo@kernel.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: rtw88: Problem with sdio.c
Date: Sat, 27 May 2023 10:15:41 +0300 [thread overview]
Message-ID: <875y8ekzxe.fsf@kernel.org> (raw)
In-Reply-To: <547524c3-bfb4-8132-b309-6eb9e648881e@lwfinger.net> (Larry Finger's message of "Wed, 24 May 2023 15:31:55 -0500")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> On 5/24/23 14:18, Jernej Škrabec wrote:
>>
>> This was fixed in:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cb0ddaaa5db09d7d216fcbf0e68779be223a1128
>
> That fix is in the kernel mainline source, but not in wireless-next,
> where I got my source. I hope it gets resolved correctly.
The fix should come to wireless-next after the next (no pun intended)
net-next pull request. One way to avoid this problem of not having all
the fixes is to use the wireless-testing tree:
https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-testing.git/
In that tree Bob Copeland periodically pulls both wireless and
wireless-next to the latest -rc releases and that way you can easily get
all the latest wireless code from one tree. For example I use
wireless-testing as the baseline for all my ath1*k drivers testing. But
do note that the tree is rebased so the history is not stable.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2023-05-27 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 18:51 rtw88: Problem with sdio.c Larry Finger
2023-05-24 19:18 ` Jernej Škrabec
2023-05-24 20:31 ` Larry Finger
2023-05-27 7:15 ` Kalle Valo [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=875y8ekzxe.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Larry.Finger@lwfinger.net \
--cc=jernej.skrabec@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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 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.