From: Greg KH <gregkh@linuxfoundation.org>
To: "J. German Rivera" <German.Rivera@freescale.com>
Cc: arnd@arndb.de, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, stuart.yoder@freescale.com,
bhupesh.sharma@freescale.com, agraf@suse.de,
bhamciu1@freescale.com, nir.erez@freescale.com,
itai.katz@freescale.com, scottwood@freescale.com,
R89243@freescale.com, dan.carpenter@oracle.com,
richard.schmitt@freescale.com
Subject: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver
Date: Fri, 12 Jun 2015 17:18:49 -0700 [thread overview]
Message-ID: <20150613001849.GB5234@kroah.com> (raw)
In-Reply-To: <1433887148-2310-1-git-send-email-German.Rivera@freescale.com>
On Tue, Jun 09, 2015 at 04:59:01PM -0500, J. German Rivera wrote:
> This patch series includes new functionality for the Freescale fsl-mc
> bus driver.
Why are people working on "new functionality" instead of working on
getting this out of the staging tree? I really hate adding new
functions to staging drivers, as this is not the correct place for
drivers to be in the tree. People should be working to get them out of
this location, and then you can add new functions to them.
So I really don't want to take this series, sorry, someone better start
working on getting this out of drivers/staging/ or I'm going to have to
drop the driver entirely from the tree.
thanks,
greg k-h
next prev parent reply other threads:[~2015-06-13 0:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 21:59 J. German Rivera
2015-06-09 21:59 ` [PATCH v4 1/7] staging: fsl-mc: MC bus IRQ support J. German Rivera
2015-06-09 21:59 ` [PATCH v4 2/7] staging: fsl_-mc: add device binding path 'driver_override' J. German Rivera
2015-06-09 21:59 ` [PATCH v4 3/7] staging: fsl-mc: Propagate driver_override for a child DPRC's children J. German Rivera
2015-06-09 21:59 ` [PATCH v4 4/7] staging: fsl-mc: Upgraded MC bus driver to match MC fw 7.0.0 J. German Rivera
2015-06-09 21:59 ` [PATCH v4 5/7] staging: fsl-mc: Allow the MC bus driver to run without GIC support J. German Rivera
2015-06-09 21:59 ` [PATCH v4 6/7] staging: fsl-mc: Add locking to serialize mc_send_command() calls J. German Rivera
2015-06-10 11:59 ` Dan Carpenter
2015-06-09 21:59 ` [PATCH v4 7/7] staging: fsl-mc: Use DPMCP IRQ and completion var to wait for MC J. German Rivera
2015-06-09 22:11 ` [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver Fabio Estevam
2015-06-09 23:07 ` Jose Rivera
2015-06-13 0:18 ` Greg KH [this message]
2015-06-13 8:46 ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver) Sudip Mukherjee
2015-06-13 16:28 ` Greg KH
2015-06-13 16:57 ` Joe Perches
2015-06-15 5:17 ` Sudip Mukherjee
2015-06-15 6:36 ` Joe Perches
2015-06-19 10:29 ` Dan Carpenter
2015-06-20 11:20 ` Sudip Mukherjee
2015-06-18 15:01 ` [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver Jose Rivera
2015-06-18 23:02 ` Greg KH
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=20150613001849.GB5234@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=German.Rivera@freescale.com \
--cc=R89243@freescale.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=bhamciu1@freescale.com \
--cc=bhupesh.sharma@freescale.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=itai.katz@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nir.erez@freescale.com \
--cc=richard.schmitt@freescale.com \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.com \
/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
all inboxes | Powered by JetHome®