All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Meng Tang <tangmeng@uniontech.com>
Cc: stable@vger.kernel.org, tony0620emma@gmail.com,
	kvalo@codeaurora.org, davem@davemloft.net, kuba@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ping-Ke Shih <pkshih@realtek.com>,
	masterzorag <masterzorag@gmail.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Kalle Valo <kvalo@kernel.org>
Subject: Re: [PATCH 5.10 v2 3/3] commit e109e3617e5d ("rtw88: rtw8821c: enable rfe 6 devices")
Date: Thu, 30 Jun 2022 13:29:37 +0200	[thread overview]
Message-ID: <Yr2JIdo6254QY8nT@kroah.com> (raw)
In-Reply-To: <20220628134351.4182-3-tangmeng@uniontech.com>

On Tue, Jun 28, 2022 at 09:43:51PM +0800, Meng Tang wrote:
> These commits can fix the problem of wifi not loading properly. At
> least in my 5.10 kernel environment, the following error message is
> reported:
> 
> rtw_8821ce 0000:01:00.0: rfe 6 isn't supported
> rtw_8821ce 0000:01:00.0: failed to setup chip efuse info
> rtw_8821ce 0000:01:00.0: failed to setup chip information
> 
> so I think that 5.10 need to merge these commits.
> 
> The patch 1/3 and patch 2/3 need to be merged synchronously, otherwise it
> will cause OE and then kernel exception.

This is not in the original commit log at all.  Shouldn't this be in the
0/3 email instead?

And yes, this hardware is not supported in the 5.10 kernel tree, please
move to 5.15 or newer and it will be fine.

thanks,

greg k-h

  reply	other threads:[~2022-06-30 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 13:43 [PATCH 5.10 v2 1/3] commit 5d6651fe8583 ("rtw88: 8821c: support RFE type2 wifi NIC") Meng Tang
2022-06-28 13:43 ` [PATCH 5.10 v2 2/3] commit b789e3fe7047 ("rtw88: 8821c: support RFE type4 " Meng Tang
2022-06-28 13:43 ` [PATCH 5.10 v2 3/3] commit e109e3617e5d ("rtw88: rtw8821c: enable rfe 6 devices") Meng Tang
2022-06-30 11:29   ` Greg KH [this message]
2022-06-30 11:28 ` [PATCH 5.10 v2 1/3] commit 5d6651fe8583 ("rtw88: 8821c: support RFE type2 wifi NIC") Greg KH

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=Yr2JIdo6254QY8nT@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masterzorag@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=stable@vger.kernel.org \
    --cc=tangmeng@uniontech.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.