linux-kernel - Re: [PATCH 0/5] MIPS: BCM47XX: Board updates from OpenWrt

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 linux-hardening linux-cve-announce 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:   Sun, 9 Jan 2022 22:43:08 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Florian Fainelli <f.fainelli@...il.com>
Cc:     linux-mips@...r.kernel.org, Hauke Mehrtens <hauke@...ke-m.de>,
        Rafał Miłecki <zajec5@...il.com>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/5] MIPS: BCM47XX: Board updates from OpenWrt

On Thu, Jan 06, 2022 at 07:51:36PM -0800, Florian Fainelli wrote:
> Hi all,
> 
> This patch is breaking up the larger patch that OpenWrt carries at:
> 
> https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/bcm47xx/patches-5.10/320-MIPS-BCM47XX-Devices-database-update-for-4.x.patch;h=bde811c1956578a33cc230b80c3a2b4a20cd9aa5;hb=HEAD
> 
> into a series of patches that add support for each board individually.
> 
> Florian Fainelli (5):
>   MIPS: BCM47XX: Define Linksys WRT310N V2 buttons
>   MIPS: BCM47XX: Add board entry for Linksys WRT320N v1
>   MIPS: BCM47XX: Add LEDs and buttons for Asus RTN-10U
>   MIPS: BCM47XX: Add support for Netgear R6300 v1
>   MIPS: BCM47XX: Add support for Netgear WN2500RP v1 & v2
> 
>  arch/mips/bcm47xx/board.c                     |  4 ++
>  arch/mips/bcm47xx/buttons.c                   | 44 +++++++++++++++++++
>  arch/mips/bcm47xx/leds.c                      | 21 +++++++++
>  .../include/asm/mach-bcm47xx/bcm47xx_board.h  |  4 ++
>  4 files changed, 73 insertions(+)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]