From: Greg KH <greg@kroah.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: Wed, 4 Feb 2015 18:29:24 -0800 [thread overview]
Message-ID: <20150205022924.GA20453@kroah.com> (raw)
In-Reply-To: <54D29A3E.9090201@Freescale.com>
On Wed, Feb 04, 2015 at 04:16:30PM -0600, Emil Medve wrote:
> Hello Greg,
>
>
> Thanks for looking at this
>
> On 02/04/2015 12:40 PM, Greg KH wrote:
> > On Wed, Feb 04, 2015 at 08:48:32AM -0600, Emil Medve wrote:
> >>
> >> Hello,
> >>
> >>
> >> This is the first attempt to publish the Freescale DPAA B/QMan drivers. They are
> >> not to be applied yet. 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
> >
> > First off, why put these in staging? What's keeping them from being
> > merged "properly"?
>
> I was thinking they'll go into drivers/soc. Past some cleanup and some
> integration issues, nothing holds them back
Then spend the day or so to do that work and avoid staging entirely!
> > Secondly, if they are going to go into staging, then I need a TODO file
> > in the directory of the driver listing what needs to be done to move the
> > code out of staging, and who is responsible for the code. Ideally a
> > MAINTAINERS entry as well.
>
> Will get both lists, say, for the next post
>
> > And finally, staging drivers should be self-contained, your .h files:
> >
> >> include/linux/fsl_bman.h | 517 +++++
> >> include/linux/fsl_qman.h | 1955 +++++++++++++++++
> >
> > Need to be in drivers/staging/<DRIVER_DIR>/ not in include/linux/
> > espeically as nothing outside of your driver needs these .h files.
>
> These files contain the public interface(s) used by other devices
> connected to the B/QMan: FMan, PME, RMan, DCE, etc. Every driver/piece
> of code in need of a HW queue (QMan) or HW buffer allocator (BMan) will
> use these files
Ok, but you can't have in-kernel code depend on staging tree code,
sorry, so if you want it in staging, it has to be self-contained. Yet
another reason for you to clean it up properly and merge it to the
correct place first.
good luck,
greg k-h
next prev parent reply other threads:[~2015-02-05 2:29 UTC|newest]
Thread overview: 24+ 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 ` Emil Medve
2015-02-04 14:48 ` [RFC 10/10] fsl_qman: " Emil Medve
2015-02-04 14:48 ` 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-04 22:16 ` Emil Medve
2015-02-05 2:29 ` Greg KH [this message]
2015-02-05 8:41 ` Dan Carpenter
2015-02-05 14:55 ` Emil Medve
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=20150205022924.GA20453@kroah.com \
--to=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.