Hi Alexander, aahringo@xxxxxxxxxx wrote on Tue, 18 Oct 2022 18:56:49 -0400: > Hi, > > On Tue, Oct 18, 2022 at 6:03 PM Miquel Raynal <miquel.raynal@xxxxxxxxxxx> wrote: > > > > Hi Alexander, > > > > aahringo@xxxxxxxxxx wrote on Tue, 18 Oct 2022 16:54:13 -0400: > > > > > Hi, > > > > > > On Tue, Oct 18, 2022 at 2:35 PM Miquel Raynal <miquel.raynal@xxxxxxxxxxx> wrote: > > > > > > > > We now have a fine grained filtering information so let's ensure proper > > > > filtering in scan mode, which means that only beacons are processed. > > > > > > > > > > Is this a fixup? Can you resend the whole series please? > > > > Hmm no? Unless I understood things the wrong way, Stefan applied > > patches 1 to 7 of my v4, and asked me to make a change on the 8th > > patch. > > > > This is v5 just for patch 8/8 of the previous series, I just changed > > a debug string actually... > > > > Okay, I see there are multiple new patches on the list, can you resend > them in one series? Then we have the right order how they need to be > applied without figuring it "somehow" out. The order should not matter much, that's why I posted them as individual patches. But no problem, I'll resent the three "followup" patches in a series. However, the patch for allowing coordinator interfaces should be considered something else, I've sent it to start discussing it as the other patches should not require a lot of review time I guess. I didn't think it made sense to wrap it in the followup series as this is mainly something new, but I'm fine doing it, the first patches can go in while we still discuss it further. > > There was a conflict when he applied it but I believe this is because > > wpan-next did not contain one of the fixes which made it to Linus' tree > > a month ago. So in my branch I still have this fix prior to this patch, > > because otherwise there will be a conflict when merging v6.1-rc1 (which > > I believe was not done yet). > > > > I see. Thanks. > > - Alex > Thanks, Miquèl
