lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 21 Jan 2022 09:27:15 +0100
From:   Miquel Raynal <>
To:     Alexander Aring <>
Cc:     Stefan Schmidt <>,
        linux-wpan - ML <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,
        "open list:NETWORKING [GENERAL]" <>,
        Xue Liu <>,
        Marcel Holtmann <>,
        Harry Morris <>,
        David Girault <>,
        Romuald Despres <>,
        Frederic Blain <>,
        Nicolas Schodet <>,
        Thomas Petazzoni <>
Subject: Re: [wpan-next v2 0/9] ieee802154: A bunch of fixes

Hi Alexander, wrote on Thu, 20 Jan 2022 17:52:57 -0500:

> Hi,
> On Thu, 20 Jan 2022 at 06:21, Miquel Raynal <> wrote:
> >
> > In preparation to a wider series, here are a number of small and random
> > fixes across the subsystem.
> >
> > Changes in v2:
> > * Fixed the build error reported by a robot. It ended up being something
> >   which I fixed in a commit from a following series. I've now sorted
> >   this out and the patch now works on its own.
> >  
> This patch series should be reviewed first and have all current
> detected fixes, it also should be tagged "wpan" (no need to fix that
> now). Then there is a following up series for a new feature which you
> like to tackle, maybe the "more generic symbol duration handling"? It
> should be based on this "fixes" patch series, Stefan will then get
> things sorted out to queue them right for upstream.
> Stefan, please correct me if I'm wrong.

Yup sorry that's not what I meant: the kernel robot detected that a
patch broke the build. This patch was part of the current series. The
issue was that I messed a copy paste error. But I didn't ran a
per-patch build test and another patch, which had nothing to do with
this fix, actually addressed the build issue. I very likely failed
something during my rebase operation.

So yes, this series should come first. Then we'll tackle the symbol
duration series, the Kconfig cleanup and after that we can start thick
topics :)

> Also, please give me the weekend to review this patch series.

Yes of course, you've been very (very) reactive so far, I try to be
also more reactive on my side but that's of course not a race!


Powered by blists - more mailing lists