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:	Wed, 18 Feb 2015 11:45:42 -0600
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Emil Medve <Emilian.Medve@...escale.com>
Cc:	linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC v2 00/10] Freescale DPAA B/QMan drivers


On Feb 16, 2015, at 9:46 AM, Emil Medve <Emilian.Medve@...escale.com> wrote:

> v2:	Moved out of staging into soc/freescale
> 
> Hello,
> 
> 
> This is the se attempt to publish the . They are
> not to be applied yet.  
> 
> These are the Freescale DPAA B/QMan drivers. At this stage, this is more or less
> the drivers from the Freescale PowerPC SDK roughly squashed and split in a
> sequence of component patches. They still needs some work and cleanup before we
> expect to have them applied, but we appreciate early feedback
> 
> To do:	Add a maintainer(s) entry
> 	Add module(s) support
> 	Some important clean-ups
> 
> Cheers,
> 
> 
> Geoff Thorpe (8):
>  fsl_bman: Add drivers for the Freescale DPAA BMan
>  fsl_qman: Add drivers for the Freescale DPAA QMan
>  powerpc/mpc85xx: Add platform support for the Freescale DPAA BMan
>  powerpc/mpc85xx: Add platform support for the Freescale DPAA QMan
>  fsl_bman: Add self-tester
>  fsl_qman: Add self-tester
>  fsl_bman: Add debugfs support
>  fsl_qman: Add debugfs support
> 
> Hai-Ying Wang (2):
>  fsl_bman: Add HOTPLUG_CPU support
>  fsl_qman: Add HOTPLUG_CPU support

Really should look at using CMA for memory reservations used by q/bman backing store.

- k--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ