linux-kernel - RE: [PATCH v2 0/5] soc/fsl/qbman: DPAA QBMan fixes and additions

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <AM6PR04MB40080234BA68140933F6B733ECE80@AM6PR04MB4008.eurprd04.prod.outlook.com>
Date:   Tue, 2 Oct 2018 06:28:46 +0000
From:   Madalin-cristian Bucur <madalin.bucur@....com>
To:     Leo Li <leoyang.li@....com>
CC:     Roy Pledge <roy.pledge@....com>,
        Claudiu Manoil <claudiu.manoil@....com>,
        Catalin Marinas <catalin.marinas@....com>,
        Scott Wood <oss@...error.net>,
        "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
        <linux-arm-kernel@...ts.infradead.org>,
        linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2 0/5] soc/fsl/qbman: DPAA QBMan fixes and additions

> -----Original Message-----
> From: Li Yang [mailto:leoyang.li@....com]
> Sent: Tuesday, October 2, 2018 1:30 AM
> To: Madalin-cristian Bucur <madalin.bucur@....com>
> Cc: Roy Pledge <roy.pledge@....com>; Claudiu Manoil
> <claudiu.manoil@....com>; Catalin Marinas <catalin.marinas@....com>; Scott
> Wood <oss@...error.net>; moderated list:ARM/FREESCALE IMX / MXC ARM
> ARCHITECTURE <linux-arm-kernel@...ts.infradead.org>; linuxppc-dev
> <linuxppc-dev@...ts.ozlabs.org>; lkml <linux-kernel@...r.kernel.org>
> Subject: Re: [PATCH v2 0/5] soc/fsl/qbman: DPAA QBMan fixes and additions
> 
> On Fri, Sep 28, 2018 at 3:44 AM Madalin Bucur <madalin.bucur@....com>
> wrote:
> >
> 
> Applied 1-4 to for-next while waiting for clarification on 5/5.   And
> updated the prefix to "soc: fsl:" style to be aligned with arm-soc
> convention.  Please try to use that style in the future for soc/fsl
> patches.

Thank you, I've sent an email about the APIs.
I'm not sure we need to align the prefix to arm-soc as the soc/fsl does not
service only ARM but also PPC based SoCs and historically we've been using
the soc/* format.

Regards,
Madalin