From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: kernel test robot <lkp@intel.com>,
Karthikeyan Kathirvel <karthikeyan.kathirvel@oss.qualcomm.com>,
ath12k@lists.infradead.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH ath-next] wifi: ath12k: allow beacon protection keys to be installed in hardware
Date: Mon, 21 Apr 2025 11:44:46 -0700 [thread overview]
Message-ID: <47ea4e64-cd87-4c42-a20d-f663f197e44c@oss.qualcomm.com> (raw)
In-Reply-To: <202504220128.2KvxCzaG-lkp@intel.com>
On 4/21/2025 10:16 AM, kernel test robot wrote:
> Hi Karthikeyan,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on d33705bb41ff786b537f8ed50a187a474db111c1]
lkp@intel.com folks:
This patch contains the following footer:
base-commit: d33705bb41ff786b537f8ed50a187a474db111c1
Depends-on: <20250421111505.3633992-1-karthikeyan.kathirvel@oss.qualcomm.com>
Is there a different mechanism needed to tell the robot about the dependency?
next prev parent reply other threads:[~2025-04-21 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250421114711.3660911-1-karthikeyan.kathirvel@oss.qualcomm.com>
2025-04-21 17:16 ` [PATCH ath-next] wifi: ath12k: allow beacon protection keys to be installed in hardware kernel test robot
2025-04-21 18:44 ` Jeff Johnson [this message]
2025-04-23 1:37 ` Philip Li
2025-04-23 18:05 ` Jeff Johnson
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=47ea4e64-cd87-4c42-a20d-f663f197e44c@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=karthikeyan.kathirvel@oss.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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