From: Kalle Valo <kvalo@codeaurora.org>
To: <yhchuang@realtek.com>
Cc: <linux-wireless@vger.kernel.org>, <pkshih@realtek.com>,
<bigeasy@linutronix.de>
Subject: Re: [PATCH v2 1/9] rtw88: 8723d: Add LC calibration
Date: Tue, 12 May 2020 08:49:43 +0000 (UTC) [thread overview]
Message-ID: <20200512084943.606F4C433BA@smtp.codeaurora.org> (raw)
In-Reply-To: <20200507042151.15634-2-yhchuang@realtek.com>
<yhchuang@realtek.com> wrote:
> From: Ping-Ke Shih <pkshih@realtek.com>
>
> LC calibration is done by hardware circuit. Driver sets the LCK bit to kick
> start, and then poll the bit to check if it's done.
>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
> Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>
Failed to apply, please rebase and send v2.
Recorded preimage for 'drivers/net/wireless/realtek/rtw88/pci.c'
error: Failed to merge in the changes.
Applying: rtw88: 8723d: Add shutdown callback to disable BT USB suspend
Using index info to reconstruct a base tree...
M drivers/net/wireless/realtek/rtw88/pci.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/wireless/realtek/rtw88/pci.c
CONFLICT (content): Merge conflict in drivers/net/wireless/realtek/rtw88/pci.c
Patch failed at 0001 rtw88: 8723d: Add shutdown callback to disable BT USB suspend
The copy of the patch that failed is found in: .git/rebase-apply/patch
9 patches set to Changes Requested.
11532385 [v2,1/9] rtw88: 8723d: Add LC calibration
11532379 [v2,2/9] rtw88: 8723d: add IQ calibration
11532393 [v2,3/9] rtw88: 8723d: Add power tracking
11532389 [v2,4/9] rtw88: 8723d: Add shutdown callback to disable BT USB suspend
11532387 [v2,5/9] rtw88: 8723d: implement flush queue
11532375 [v2,6/9] rtw88: 8723d: set ltecoex register address in chip_info
11532377 [v2,7/9] rtw88: 8723d: Add coex support
11532383 [v2,8/9] rtw88: fill zeros to words 0x06 and 0x07 of security cam entry
11532381 [v2,9/9] rtw88: 8723d: Add 8723DE to Kconfig and Makefile
--
https://patchwork.kernel.org/patch/11532385/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-05-12 8:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 4:21 [PATCH v2 0/9] rtw88: 8723d: Add RF calibration and coex yhchuang
2020-05-07 4:21 ` [PATCH v2 1/9] rtw88: 8723d: Add LC calibration yhchuang
2020-05-12 8:49 ` Kalle Valo [this message]
2020-05-07 4:21 ` [PATCH v2 2/9] rtw88: 8723d: add IQ calibration yhchuang
2020-05-07 4:21 ` [PATCH v2 3/9] rtw88: 8723d: Add power tracking yhchuang
2020-05-07 4:21 ` [PATCH v2 4/9] rtw88: 8723d: Add shutdown callback to disable BT USB suspend yhchuang
2020-05-07 4:21 ` [PATCH v2 5/9] rtw88: 8723d: implement flush queue yhchuang
2020-05-07 4:21 ` [PATCH v2 6/9] rtw88: 8723d: set ltecoex register address in chip_info yhchuang
2020-05-07 4:21 ` [PATCH v2 7/9] rtw88: 8723d: Add coex support yhchuang
2020-05-07 4:21 ` [PATCH v2 8/9] rtw88: fill zeros to words 0x06 and 0x07 of security cam entry yhchuang
2020-05-07 4:21 ` [PATCH v2 9/9] rtw88: 8723d: Add 8723DE to Kconfig and Makefile yhchuang
2020-05-11 19:07 ` kbuild test robot
2020-05-11 19:07 ` [RFC PATCH] rtw88: 8723d: rtw8723d_pwr_track() can be static kbuild test robot
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=20200512084943.606F4C433BA@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=bigeasy@linutronix.de \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=yhchuang@realtek.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;
as well as URLs for NNTP newsgroup(s).