From: Johannes Berg <johannes@sipsolutions.net>
To: "Jérôme Pouiller" <jerome.pouiller@silabs.com>,
linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Kalle Valo <kvalo@kernel.org>,
linux-devel@silabs.com
Subject: Re: [PATCH v2 0/5] wfx: add support for WoWLAN on Silabs WF200
Date: Thu, 06 Mar 2025 09:37:04 +0100 [thread overview]
Message-ID: <348c5c7840db255e6cdccb566f7cc3042dd18799.camel@sipsolutions.net> (raw)
In-Reply-To: <47066295.fMDQidcC6G@nb0018864>
On Thu, 2025-03-06 at 09:35 +0100, Jérôme Pouiller wrote:
>
> I though the missing target tree name was a blocker.
>
Ah, no. That's just because it doesn't _always_ manage to apply it. It's
only a blocker if that's the only thing it reported, but here it just
said it was missing but went ahead anyway.
Honestly, I have no idea why all that is, sorry.
johannes
prev parent reply other threads:[~2025-03-06 8:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 14:47 Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 1/5] wifi: wfx: align declarations between bus_spi.c and bus_sdio.c Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 2/5] wifi: wfx: declare support for WoWLAN Jérôme Pouiller
2025-03-03 15:05 ` kernel test robot
2025-03-03 16:28 ` kernel test robot
2025-03-02 14:47 ` [PATCH v2 3/5] wifi: wfx: allow SPI device to wake up the host Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 4/5] wifi: wfx: allow SDIO " Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 5/5] wifi: wfx: allow to enable WoWLAN using NL80211 Jérôme Pouiller
2025-03-03 8:20 ` [PATCH v2 0/5] wfx: add support for WoWLAN on Silabs WF200 Johannes Berg
2025-03-04 15:22 ` Jérôme Pouiller
2025-03-05 7:40 ` Johannes Berg
2025-03-05 15:18 ` Jérôme Pouiller
2025-03-06 8:10 ` Johannes Berg
2025-03-06 8:35 ` Jérôme Pouiller
2025-03-06 8:37 ` Johannes Berg [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=348c5c7840db255e6cdccb566f7cc3042dd18799.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jerome.pouiller@silabs.com \
--cc=kvalo@kernel.org \
--cc=linux-devel@silabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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
all inboxes | Powered by JetHome®