From: Harshitha Prem <quic_hprem@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>, Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/8] wifi: ath12k: Introduce device group abstraction
Date: Wed, 24 Apr 2024 10:17:03 +0530 [thread overview]
Message-ID: <cf025908-8e88-f60c-6466-9fdf1bccff09@quicinc.com> (raw)
In-Reply-To: <8734rbidcg.fsf@kernel.org>
On 4/24/2024 10:09 AM, Kalle Valo wrote:
> Jeff Johnson <quic_jjohnson@quicinc.com> writes:
>
>>>> Depends-on:
>>>> [PATCH 0/3] wifi: ath12k: Refactor the hardware recovery
>>>> procedures
>>>
>>> Are you referring to this patchset:
>>>
>>> https://patchwork.kernel.org/project/linux-wireless/list/?series=821155&state=*&order=date
>>>
>>> That was sent three months ago and at least I couldn't find a newer
>>> version. So I'll just drop this patchset for now without even looking at
>>> it.
>>>
>>
>> Yes, I'm stumped as well. the patch specifies:
>>> base-commit: c416602943dd36fbd13af7496430723935c867a3
>>> prerequisite-patch-id: a4d62344b11368fb7e549c03b6a31f7ba4c9e2bb
>>> prerequisite-patch-id: b4a1e18a85d8c1e337fa133c2bd2956c33b11046
>>> prerequisite-patch-id: b16edd310baa35e2500267e338f60c9a2e6594e1
>>
>> but lore is unable to find those prerequisite patch-ids, which leads me to
>> believe that they were rebased internally but never posted.
>>
>> I tried to apply the January series on top of the base-commit:
>> c416602943dd36fbd13af7496430723935c867a3 but it doesn't apply cleanly.
>>
>> So I think we need to have a rebased and updated "Refactor the hardware
>> recovery procedures" first.
>
> Yeah, it's waste of everyone's time to submit patches like this which
> don't even apply at all due to missing dependencies. Please don't do
> that.
>
Sure. Sorry Jeff and Kalle, My bad!. yes,the dependent patch should be
rebased. Will respawn this series after the dependencies are at the latest.
Thanks,
Harshitha
prev parent reply other threads:[~2024-04-24 4:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 8:37 [PATCH 0/8] wifi: ath12k: Introduce device group abstraction Harshitha Prem
2024-04-20 8:37 ` [PATCH 1/8] wifi: ath12k: Refactor core start api Harshitha Prem
2024-04-20 8:37 ` [PATCH 2/8] wifi: ath12k: Add helpers to get or set ath12k_hw Harshitha Prem
2024-04-20 8:37 ` [PATCH 3/8] wifi: ath12k: Add ath12k_get_num_hw api Harshitha Prem
2024-04-20 8:37 ` [PATCH 4/8] wifi: ath12k: Introduce QMI firmware ready flag Harshitha Prem
2024-04-20 8:37 ` [PATCH 5/8] wifi: ath12k: move ATH12K_FLAG_REGISTERED flag set to mac_register api Harshitha Prem
2024-04-20 8:37 ` [PATCH 6/8] wifi: ath12k: Introduce device group abstraction Harshitha Prem
2024-04-20 8:37 ` [PATCH 7/8] wifi: ath12k: refactor core start based on hardware group Harshitha Prem
2024-04-20 8:37 ` [PATCH 8/8] wifi: ath12k: move ath12k_hw from per soc to group Harshitha Prem
2024-04-23 9:39 ` [PATCH 0/8] wifi: ath12k: Introduce device group abstraction Kalle Valo
2024-04-23 21:24 ` Jeff Johnson
2024-04-24 4:39 ` Kalle Valo
2024-04-24 4:47 ` Harshitha Prem [this message]
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=cf025908-8e88-f60c-6466-9fdf1bccff09@quicinc.com \
--to=quic_hprem@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.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 read-only IMAP folder(s) and NNTP newsgroup(s).