From: Kalle Valo <kvalo@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>,
Baochen Qiang <quic_bqiang@quicinc.com>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 2/2] wifi: ath11k: add support for QCA2066
Date: Fri, 12 Jan 2024 17:46:54 +0200 [thread overview]
Message-ID: <874jfia70x.fsf@kernel.org> (raw)
In-Reply-To: <20240112-dangerous-cow-of-excitement-fdbaa6@lemur> (Konstantin Ryabitsev's message of "Fri, 12 Jan 2024 09:38:22 -0500")
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> On Wed, Jan 10, 2024 at 08:20:46AM -0800, Jeff Johnson wrote:
>> Unfortunately automated tasks don't parse cover letters. But it looks
>> like b4 doesn't handle or warn about:
>> prerequisite-patch-id: 640366721125b1adea0eeabd5cdfca5e91476e7c
>>
>> And not quite sure how it would handle that.
>
> B4 should be able to handle dependencies like that in the future. For example,
> we can already locate this patch using:
>
> https://lore.kernel.org/all/?q=patchid%3A640366721125b1adea0eeabd5cdfca5e91476e7c
Oh, that is a very useful feature. Thank you.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-01-12 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 2:13 [PATCH v2 0/2] wifi: ath11k: add support for QCA2066 Baochen Qiang
2024-01-09 2:13 ` [PATCH v2 1/2] wifi: ath11k: move pci.ops registration ahead Baochen Qiang
2024-02-15 11:24 ` Kalle Valo
2024-01-09 2:13 ` [PATCH v2 2/2] wifi: ath11k: add support for QCA2066 Baochen Qiang
2024-01-09 17:41 ` Jeff Johnson
2024-01-10 2:16 ` Baochen Qiang
2024-01-10 16:20 ` Jeff Johnson
2024-01-11 17:04 ` Kalle Valo
2024-01-12 14:38 ` Konstantin Ryabitsev
2024-01-12 15:46 ` Kalle Valo [this message]
2024-01-09 12:21 ` [PATCH v2 0/2] " Kalle Valo
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=874jfia70x.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@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 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.