From: Johannes Berg <johannes@sipsolutions.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-next-2022-03-11
Date: Mon, 14 Mar 2022 21:45:11 +0100 [thread overview]
Message-ID: <3e9e10f34215b4d6b3a7361971df3c93d4b25419.camel@sipsolutions.net> (raw)
In-Reply-To: <20220314134146.20fef5b9@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Mon, 2022-03-14 at 13:41 -0700, Jakub Kicinski wrote:
>
> Depends on what you mean. The bot currently understands the netdev +
> bpf pw instance so it determines the target tree between those four.
Makes sense, that's what it was written for :)
On the linux-wireless patchwork instance
(https://patchwork.kernel.org/project/linux-wireless/) there are only
two trees now, I think, wireless/main and wireless-next/main. Perhaps
mt76 but maybe we'll just bring those into the fold too. Oh, I guess
Kalle has some ath* trees too, not sure now.
> We'd need to teach it how to handle more trees, which would be a great
> improvement, but requires coding.
Right. Do you have it out in the open somewhere? Maybe we could even
take it and run our own instance somewhere.
> > But I do't know who runs it, how it runs, who's paying for it, etc.
>
> Yeah... As much as I'd love to give you root on the VM having it under
> the corporate account is the only way I can get it paid for :(
Right.
Anyway, was just thinking out loud I guess.
johannes
next prev parent reply other threads:[~2022-03-14 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 12:40 pull-request: wireless-next-2022-03-11 Johannes Berg
2022-03-11 21:05 ` Jakub Kicinski
2022-03-14 18:20 ` Kalle Valo
2022-03-11 21:20 ` patchwork-bot+netdevbpf
2022-03-12 1:06 ` Jakub Kicinski
2022-03-12 1:08 ` Jakub Kicinski
2022-03-14 18:21 ` Kalle Valo
2022-03-14 18:37 ` Jakub Kicinski
2022-03-14 20:17 ` Johannes Berg
2022-03-14 20:41 ` Jakub Kicinski
2022-03-14 20:45 ` Johannes Berg [this message]
2022-03-14 20:51 ` Jakub Kicinski
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=3e9e10f34215b4d6b3a7361971df3c93d4b25419.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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