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: <20161206095800.GA4247@kroah.com>
Date:   Tue, 6 Dec 2016 10:58:00 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Ioana Radulescu <ruxandra.radulescu@....com>
Cc:     devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
        agraf@...e.de, arnd@...db.de, alexandru.marginean@....com,
        bogdan.hamciuc@....com, stuart.yoder@....com, roy.pledge@....com,
        laurentiu.tudor@....com
Subject: Re: [PATCH 7/8] staging: fsl-dpaa2/eth: Add TODO file

On Tue, Dec 06, 2016 at 03:34:41AM -0600, Ioana Radulescu wrote:
> Add a list of TODO items for the Ethernet driver
> 
> Signed-off-by: Ioana Radulescu <ruxandra.radulescu@....com>
> ---
>  drivers/staging/fsl-dpaa2/ethernet/TODO |    9 +++++++++
>  1 files changed, 9 insertions(+), 0 deletions(-)
>  create mode 100644 drivers/staging/fsl-dpaa2/ethernet/TODO
> 
> diff --git a/drivers/staging/fsl-dpaa2/ethernet/TODO b/drivers/staging/fsl-dpaa2/ethernet/TODO
> new file mode 100644
> index 0000000..833265b
> --- /dev/null
> +++ b/drivers/staging/fsl-dpaa2/ethernet/TODO
> @@ -0,0 +1,9 @@
> +* Add a DPAA2 MAC kernel driver in order to allow PHY management; currently
> +  the DPMAC objects and their link to DPNIs are handled by MC internally
> +  and all PHYs are seen as fixed-link
> +* add more debug support: decide how to expose detailed debug statistics,
> +  add ingress error queue support
> +* MC firmware uprev; the DPAA2 objects used by the Ethernet driver need to
> +  be kept in sync with binary interface changes in MC
> +* refine README file
> +* cleanup

These seem like very minor things, why not just spend a week and do this
work and get it merged to the "correct" portion of the kernel tree?  Why
does this have to go into staging?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ