lists.openwall.net   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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 04 Jun 2019 20:11:22 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     rasmus.villemoes@...vas.dk
Cc:     andrew@...n.ch, vivien.didelot@...il.com, f.fainelli@...il.com,
        robh+dt@...nel.org, mark.rutland@....com, netdev@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        Rasmus.Villemoes@...vas.se
Subject: Re: [PATCH net-next v4 00/10] net: dsa: mv88e6xxx: support for
 mv88e6250

From: Rasmus Villemoes <rasmus.villemoes@...vas.dk>
Date: Tue, 4 Jun 2019 07:34:22 +0000

> This adds support for the mv88e6250 chip. Initially based on the
> mv88e6240, this time around, I've been through each ->ops callback and
> checked that it makes sense, either replacing with a 6250 specific
> variant or dropping it if no equivalent functionality seems to exist
> for the 6250. Along the way, I found a few oddities in the existing
> code, mostly sent as separate patches/questions.
> 
> The one relevant to the 6250 is the ieee_pri_map callback, where the
> existing mv88e6085_g1_ieee_pri_map() is actually wrong for many of the
> existing users. I've put the mv88e6250_g1_ieee_pri_map() patch first
> in case some of the existing chips get switched over to use that and
> it is deemed important enough for -stable.
 ...

Series applied, thanks.

Powered by blists - more mailing lists