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  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:   Thu, 2 Nov 2017 16:57:55 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Sebastien Bourdelin <sebastien.bourdelin@...oirfairelinux.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        kernel <kernel@...oirfairelinux.com>,
        Rob Herring <robh@...nel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Fabio Estevam <fabio.estevam@....com>,
        Mark Featherston <mark@...eddedarm.com>, kris@...eddedarm.com
Subject: Re: [PATCH v7 2/2] bus: add driver for the Technologic Systems NBUS

On Thu, Nov 2, 2017 at 3:37 PM, Sebastien Bourdelin
<sebastien.bourdelin@...oirfairelinux.com> wrote:

>> BTW do you have a way upstream for this patch? ARM SoC?
>
> Honestly i have no idea, do you have a recommandation for this kind of
> bus driver? should i re-submit just this patch to a specific tree?

If this is for an ARM system I would suggest that you just sent
the patches to arm@...nel.org with CC to the linux-arm-kernel
mailing list and ask the ARM SoC maintainers to apply them directly
for the upstream kernel.

Yours,
Linus Walleij

Powered by blists - more mailing lists