public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Harshitha Prem <quic_hprem@quicinc.com>,
	 <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 07:39:11 +0300	[thread overview]
Message-ID: <8734rbidcg.fsf@kernel.org> (raw)
In-Reply-To: <57002bbf-2c85-4fa7-b249-4bd3f2ba1bcf@quicinc.com> (Jeff Johnson's message of "Tue, 23 Apr 2024 14:24:12 -0700")

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.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

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


  reply	other threads:[~2024-04-24  4:39 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 [this message]
2024-04-24  4:47       ` Harshitha Prem

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=8734rbidcg.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_hprem@quicinc.com \
    --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