From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Philip Li <philip.li@intel.com>
Cc: kernel test robot <lkp@intel.com>,
Karthikeyan Kathirvel <karthikeyan.kathirvel@oss.qualcomm.com>,
ath12k@lists.infradead.org, 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: Wed, 23 Apr 2025 11:05:58 -0700 [thread overview]
Message-ID: <99d239c6-e276-4a16-b7db-6e1f8ecc0bf6@oss.qualcomm.com> (raw)
In-Reply-To: <aAhEc8yrW4vcrE7J@rli9-mobl>
On 4/22/2025 6:37 PM, Philip Li wrote:
> On Mon, Apr 21, 2025 at 11:44:46AM -0700, Jeff Johnson wrote:
>> 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?
>
> Sorry for confusion, for now if there's base-commit specified, the bot would
> only consider it as the base and apply the patch. And actually, if there's
> a dependency specified by link, the bot so far can't recognize it well.
>
> BTW: for this case, does it mean the patch need be applied on this "Depends-on"
> patch, and this "Depends-on" patch is on top of the base-commit?
In this case the Depends-on patch is applied on top of the base patch, and
then the actual patch is applied on top of that.
/jeff
next prev parent reply other threads:[~2025-04-23 18:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 11:47 [PATCH ath-next] wifi: ath12k: allow beacon protection keys to be installed in hardware Karthikeyan Kathirvel
2025-04-21 17:16 ` kernel test robot
2025-04-21 18:44 ` Jeff Johnson
2025-04-23 1:37 ` Philip Li
2025-04-23 18:05 ` Jeff Johnson [this message]
2025-04-22 9:48 ` kernel test robot
2025-04-29 15:47 ` Nicolas Escande
2025-04-30 6:05 ` Karthikeyan Kathirvel
2025-05-09 16:07 ` Jeff Johnson
2025-06-04 8:59 ` Karthikeyan Kathirvel
2025-06-04 20:38 ` Jeff Johnson
2025-06-06 13:22 ` Karthikeyan Kathirvel
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=99d239c6-e276-4a16-b7db-6e1f8ecc0bf6@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 \
--cc=philip.li@intel.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