From: Dan Carpenter <dan.carpenter@oracle.com>
To: Emil Medve <Emilian.Medve@Freescale.com>
Cc: devel@driverdev.osuosl.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 00/10] Freescale DPAA B/QMan drivers
Date: Thu, 5 Feb 2015 11:41:14 +0300 [thread overview]
Message-ID: <20150205084114.GC5336@mwanda> (raw)
In-Reply-To: <1423061322-16059-1-git-send-email-Emilian.Medve@Freescale.com>
Normally, for staging drivers we just require the TODO and a maintainer
and we merge things as-is. There isn't really much review of the code.
regards,
dan carpenter
next prev parent reply other threads:[~2015-02-05 8:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 14:48 [RFC 00/10] Freescale DPAA B/QMan drivers Emil Medve
2015-02-04 14:48 ` [RFC 01/10] fsl_bman: Add drivers for the Freescale DPAA BMan Emil Medve
2015-02-04 14:48 ` [RFC 02/10] fsl_qman: Add drivers for the Freescale DPAA QMan Emil Medve
2015-02-04 14:48 ` [RFC 03/10] powerpc/mpc85xx: Add platform support for the Freescale DPAA BMan Emil Medve
2015-02-04 14:48 ` [RFC 04/10] powerpc/mpc85xx: Add platform support for the Freescale DPAA QMan Emil Medve
2015-02-04 14:48 ` [RFC 05/10] fsl_bman: Add self-tester Emil Medve
2015-02-04 14:48 ` [RFC 06/10] fsl_qman: " Emil Medve
2015-02-04 14:48 ` [RFC 07/10] fsl_bman: Add debugfs support Emil Medve
2015-02-04 14:48 ` [RFC 08/10] fsl_qman: " Emil Medve
2015-02-04 14:48 ` [RFC 09/10] fsl_bman: Add HOTPLUG_CPU support Emil Medve
2015-02-04 14:48 ` [RFC 10/10] fsl_qman: " Emil Medve
2015-02-04 18:40 ` [RFC 00/10] Freescale DPAA B/QMan drivers Greg KH
2015-02-04 22:16 ` Emil Medve
2015-02-05 2:29 ` Greg KH
2015-02-05 8:41 ` Dan Carpenter [this message]
2015-02-05 14:55 ` Emil Medve
2015-02-05 15:48 ` Bob Cochran
2015-02-05 15:52 ` Emil Medve
2015-02-20 14:43 ` Bob Cochran
2015-02-20 14:57 ` Joakim Tjernlund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150205084114.GC5336@mwanda \
--to=dan.carpenter@oracle.com \
--cc=Emilian.Medve@Freescale.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).