From: Kalle Valo <kvalo@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: David Ruth <druth@chromium.org>,
nbd@nbd.name, lorenzo@kernel.org,
oe-kbuild-all@lists.linux.dev, linux-wireless@vger.kernel.org,
timvp@chromium.org, sean.wang@mediatek.com,
ryder.lee@mediatek.com, shayne.chen@mediatek.com
Subject: Re: [PATCH] wifi: mt76: mt7921: Cancel scan work on unregister.
Date: Wed, 07 Aug 2024 15:08:58 +0300 [thread overview]
Message-ID: <87plqkilgl.fsf@kernel.org> (raw)
In-Reply-To: <202408071730.Ux9Cr643-lkp@intel.com> (kernel test robot's message of "Wed, 7 Aug 2024 18:31:09 +0800")
kernel test robot <lkp@intel.com> writes:
> Hi David,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on wireless-next/main]
> [also build test ERROR on wireless/main linus/master v6.11-rc2 next-20240807]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
I suspect this should be tested on top of Felix's tree:
MEDIATEK MT76 WIRELESS LAN DRIVER
M: Felix Fietkau <nbd@nbd.name>
M: Lorenzo Bianconi <lorenzo@kernel.org>
M: Ryder Lee <ryder.lee@mediatek.com>
R: Shayne Chen <shayne.chen@mediatek.com>
R: Sean Wang <sean.wang@mediatek.com>
L: linux-wireless@vger.kernel.org
S: Maintained
T: git https://github.com/nbd168/wireless
F: Documentation/devicetree/bindings/net/wireless/mediatek,mt76.yaml
F: drivers/net/wireless/mediatek/mt76/
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
Yeah, using --base is very much recommended.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-08-07 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 22:21 [PATCH] wifi: mt76: mt7921: Cancel scan work on unregister David Ruth
2024-08-07 9:19 ` kernel test robot
2024-08-07 10:31 ` kernel test robot
2024-08-07 12:08 ` Kalle Valo [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=87plqkilgl.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=druth@chromium.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=timvp@chromium.org \
/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 NNTP newsgroup(s).