From: Ping-Ke Shih <pkshih@realtek.com>
To: kernel test robot <lkp@intel.com>, "kvalo@kernel.org" <kvalo@kernel.org>
Cc: "oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"Kevin Yang" <kevin_yang@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH 1/6] wifi: rtw89: mcc: initialize start flow
Date: Thu, 31 Aug 2023 02:40:37 +0000 [thread overview]
Message-ID: <649b583bd1da41bd895cb84345485af9@realtek.com> (raw)
In-Reply-To: <202308302155.2snig4j9-lkp@intel.com>
> -----Original Message-----
> From: kernel test robot <lkp@intel.com>
> Sent: Wednesday, August 30, 2023 9:25 PM
> To: Ping-Ke Shih <pkshih@realtek.com>; kvalo@kernel.org
> Cc: oe-kbuild-all@lists.linux.dev; Kevin Yang <kevin_yang@realtek.com>; linux-wireless@vger.kernel.org
> Subject: Re: [PATCH 1/6] wifi: rtw89: mcc: initialize start flow
>
> >> ERROR: modpost: "__umoddi3" [drivers/net/wireless/realtek/rtw89/rtw89_core.ko] undefined!
I will use div_u64_rem() instead, and send v2.
Ping-Ke
next prev parent reply other threads:[~2023-08-31 2:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 2:19 [PATCH 0/6] wifi: rtw89: prepare timeslot and trigger firmware for MCC Ping-Ke Shih
2023-08-29 2:19 ` [PATCH 1/6] wifi: rtw89: mcc: initialize start flow Ping-Ke Shih
2023-08-30 13:25 ` kernel test robot
2023-08-31 2:40 ` Ping-Ke Shih [this message]
2023-08-29 2:19 ` [PATCH 2/6] wifi: rtw89: mcc: fill fundamental configurations Ping-Ke Shih
2023-08-29 2:19 ` [PATCH 3/6] wifi: rtw89: mcc: consider and determine BT duration Ping-Ke Shih
2023-08-29 2:19 ` [PATCH 4/6] wifi: rtw89: mcc: decide pattern and calculate parameters Ping-Ke Shih
2023-08-29 2:19 ` [PATCH 5/6] wifi: rtw89: fix typo of rtw89_fw_h2c_mcc_macid_bitmap() Ping-Ke Shih
2023-08-29 2:19 ` [PATCH 6/6] wifi: rtw89: mcc: trigger FW to start/stop MCC 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=649b583bd1da41bd895cb84345485af9@realtek.com \
--to=pkshih@realtek.com \
--cc=kevin_yang@realtek.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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).