All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: David Rubio <david.alejandro.rubio@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Andy Huang <tehuang@realtek.com>,
	Brian Norris <briannorris@chromium.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Yan-Hsuan Chuang <tony0620emma@gmail.com>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: Re: rtw88 / rtl_8821ce: rfe 2 is not supported
Date: Mon, 19 Oct 2020 10:37:07 +0300	[thread overview]
Message-ID: <87y2k2hdjw.fsf@codeaurora.org> (raw)
In-Reply-To: <CAO6ttSkXSt3UC5P-RDCDUhDC66MRb5UkvCcbT5POzkve9G=GyA@mail.gmail.com> (David Rubio's message of "Sun, 18 Oct 2020 19:51:42 -0300")

David Rubio <david.alejandro.rubio@gmail.com> writes:

> There's no possibility of including it on 5.10 changes? Seems like a
> trivial patch Or did the merge window pass already? I'm not aware of
> it by now.

wireless-drivers-next goes via net-next and the deadline for net-next is
before the merge window opens, so it's too late for v5.10.

-- 
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2020-10-19  7:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11 16:13 rtw88 / rtl_8821ce: rfe 2 is not supported David Rubio
2020-10-12 18:12 ` Brian Norris
2020-10-13  2:11   ` Andy Huang
2020-10-13  2:37     ` Larry Finger
2020-10-16 18:42       ` David Rubio
2020-10-18  9:11         ` Kalle Valo
2020-10-18 22:51           ` David Rubio
2020-10-19  7:37             ` Kalle Valo [this message]
2020-10-19 17:10           ` Larry Finger
2020-10-19 17:42             ` David Rubio
2020-10-21  3:41               ` Andy Huang
2020-10-21 14:12                 ` David Rubio
2020-10-22  5:53             ` Kalle Valo
2020-10-22 15:53               ` Larry Finger
2020-10-23  3:13                 ` Andy Huang

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=87y2k2hdjw.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=briannorris@chromium.org \
    --cc=david.alejandro.rubio@gmail.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tehuang@realtek.com \
    --cc=tony0620emma@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 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.