From: Greg KH <gregkh@linuxfoundation.org>
To: laurentiu.tudor@nxp.com
Cc: ruxandra.radulescu@nxp.com, stuyoder@gmail.com,
devel@driverdev.osuosl.org, Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Stuart Yoder <stuart.yoder@nxp.com>,
roy.pledge@nxp.com, linux-kernel@vger.kernel.org,
leoyang.li@nxp.com, Thomas Gleixner <tglx@linutronix.de>,
bogdan.purcareata@nxp.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] staging: fsl-mc: move bus driver out of staging
Date: Tue, 22 Aug 2017 18:39:47 -0700 [thread overview]
Message-ID: <20170823013947.GB10615@kroah.com> (raw)
In-Reply-To: <20170819171812.21902-1-laurentiu.tudor@nxp.com>
On Sat, Aug 19, 2017 at 08:18:12PM +0300, laurentiu.tudor@nxp.com wrote:
> From: Stuart Yoder <stuart.yoder@nxp.com>
>
> Move the source files out of staging into their final locations:
> -include files in drivers/staging/fsl-mc/include go to include/linux/fsl
> -irq-gic-v3-its-fsl-mc-msi.c goes to drivers/irqchip
> -source in drivers/staging/fsl-mc/bus goes to drivers/bus/fsl-mc
> -README.txt, providing and overview of DPAA goes to
> Documentation/dpaa2/overview.txt
>
> Update or delete other remaining staging files-- Makefile, Kconfig, TODO.
> Update dpaa2_eth and dpio staging drivers.
>
> Signed-off-by: Stuart Yoder <stuyoder@gmail.com>
> Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com>
> [Laurentiu: rebased, add dpaa2_eth and dpio #include updates]
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Jason Cooper <jason@lakedaemon.net>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
Really? You all have fixed all of the previous issues found? Is it
time for another real review? If so, please ask for it.
thanks,
greg k-h
next prev parent reply other threads:[~2017-08-23 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 17:18 [PATCH] staging: fsl-mc: move bus driver out of staging laurentiu.tudor
2017-08-23 1:39 ` Greg KH [this message]
2017-08-23 9:08 ` Laurentiu Tudor
2017-08-23 7:56 ` Marc Zyngier
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=20170823013947.GB10615@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bogdan.purcareata@nxp.com \
--cc=devel@driverdev.osuosl.org \
--cc=jason@lakedaemon.net \
--cc=laurentiu.tudor@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=roy.pledge@nxp.com \
--cc=ruxandra.radulescu@nxp.com \
--cc=stuart.yoder@nxp.com \
--cc=stuyoder@gmail.com \
--cc=tglx@linutronix.de \
/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