From: Ping-Ke Shih <pkshih@realtek.com>
To: Tim K <tpkuester@gmail.com>
Cc: "Marcin Ślusarz" <marcin.slusarz@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Marcin Ślusarz" <mslusarz@renau.com>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
"Kalle Valo" <kvalo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw88: schedule rx work after everything is set up
Date: Tue, 2 Jul 2024 03:15:24 +0000 [thread overview]
Message-ID: <2c4974e113474cea87ff276eff09c882@realtek.com> (raw)
In-Reply-To: CA+shoWSt44WxS6s=z8wR3AMRYFj9tuxWdkwVLG5i2mU34jn4Xw@mail.gmail.com
Hi Tim,
Ping-Ke Shih wrote:
> Tim K <tpkuester@gmail.com> wrote:
> >
> > > I gave this suggestions too early, since we have not gotten test result from Tim.
> > > I will change them to "Link:" if no ACK from Tim while merging.
> >
> > Hey all, thanks for reaching out!
> >
> > Sadly I'm not able to work on this project right now, but I've
> > forwarded this email to a few colleagues to bring them in the loop.
> > Did you have a timeline you were looking at to close this off?
>
> Thanks for your reply. I would take this patch to 6.11, so you have about
> 4-5 weeks. Is it enough to you?
Do you have any update on this patch?
Ping-Ke
next prev parent reply other threads:[~2024-07-02 3:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 17:01 [PATCH] wifi: rtw88: schedule rx work after everything is set up marcin.slusarz
2024-05-27 17:17 ` Kalle Valo
2024-05-28 2:50 ` Ping-Ke Shih
2024-05-28 3:00 ` Ping-Ke Shih
2024-05-28 11:02 ` Marcin Ślusarz
2024-05-29 1:28 ` Ping-Ke Shih
2024-05-30 14:33 ` Tim K
2024-05-31 0:35 ` Ping-Ke Shih
2024-07-02 3:15 ` Ping-Ke Shih [this message]
2024-07-05 1:45 ` Ping-Ke Shih
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=2c4974e113474cea87ff276eff09c882@realtek.com \
--to=pkshih@realtek.com \
--cc=Larry.Finger@lwfinger.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=mslusarz@renau.com \
--cc=tpkuester@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