[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6d37b8c3415b88ff6da1b88f0c6dfb649824311c.camel@sipsolutions.net>
Date: Mon, 14 Mar 2022 21:17:30 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Jakub Kicinski <kuba@...nel.org>, Kalle Valo <kvalo@...nel.org>
Cc: netdev@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: pull-request: wireless-next-2022-03-11
On Mon, 2022-03-14 at 11:37 -0700, Jakub Kicinski wrote:
> On Mon, 14 Mar 2022 20:21:53 +0200 Kalle Valo wrote:
> > Jakub Kicinski <kuba@...nel.org> writes:
> >
> > > On Fri, 11 Mar 2022 17:06:25 -0800 Jakub Kicinski wrote:
> > > > Seems to break clang build.
> > >
> > > No, sorry just some new warnings with W=1, I think.
> >
> > I have not installed clang yet. You don't happen to have the warnings
> > stored someplace? I checked the patchwork tests and didn't see anything
> > there.
>
> Yeah.. patchwork build thing can't resolve conflicts. I wish there was
> a way to attach a resolution to the PR so that the bot can use it :S
>
That'd be on thing - but OTOH ... maybe you/we could somehow attach the
bot that processes things on the netdev patchwork also to the wireless
one? It's on the same patchwork instance already, so ...
But I do't know who runs it, how it runs, who's paying for it, etc.
johannes
Powered by blists - more mailing lists