From: Greg KH <gregkh@linuxfoundation.org>
To: Bogdan Purcareata <bogdan.purcareata@nxp.com>
Cc: devel@driverdev.osuosl.org, robh@kernel.org, stuyoder@gmail.com,
arnd@arndb.de, marc.zyngier@arm.com, roy.pledge@nxp.com,
linux-kernel@vger.kernel.org, razvan.stefanescu@nxp.com,
horia.geanta@nxp.com, nipun.gupta@nxp.com, ioana.ciornei@nxp.com,
tglx@linutronix.de, jason@lakedaemon.net,
linux-arm-kernel@lists.infradead.org, laurentiu.tudor@nxp.com
Subject: Re: [PATCH v6 0/2] staging: fsl-mc: Move bus driver out of staging
Date: Thu, 22 Feb 2018 15:12:17 +0100 [thread overview]
Message-ID: <20180222141217.GA19330@kroah.com> (raw)
In-Reply-To: <20180205140743.29974-1-bogdan.purcareata@nxp.com>
On Mon, Feb 05, 2018 at 08:07:41AM -0600, Bogdan Purcareata wrote:
> Previous submission: https://lkml.org/lkml/2018/1/26/215
>
> Split the code into moving out the core bus infrastructure separate from
> the irqchip glue code. Add a Kconfig dependency on ARM_GIC_V3_ITS.
> Integrate the documentation with the kernel build system.
>
> This patchset only handles moving the fsl-mc bus core out of staging.
> The remaining objects (DPBP, DPCON) and drivers (dpio, dpaa2-eth) will
> be moved out in subsequent patches.
Now applied, nice work everyone.
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2018-02-22 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 14:07 [PATCH v6 0/2] staging: fsl-mc: Move bus driver out of staging Bogdan Purcareata
2018-02-05 14:07 ` [PATCH v6 1/2] staging: fsl-mc: Move core bus " Bogdan Purcareata
2018-02-06 7:18 ` Horia Geantă
2018-02-06 8:57 ` Bogdan Purcareata
2018-02-05 14:07 ` [PATCH v6 2/2] staging: fsl-mc: Move irqchip code " Bogdan Purcareata
2018-02-22 14:12 ` Greg KH [this message]
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=20180222141217.GA19330@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=bogdan.purcareata@nxp.com \
--cc=devel@driverdev.osuosl.org \
--cc=horia.geanta@nxp.com \
--cc=ioana.ciornei@nxp.com \
--cc=jason@lakedaemon.net \
--cc=laurentiu.tudor@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=nipun.gupta@nxp.com \
--cc=razvan.stefanescu@nxp.com \
--cc=robh@kernel.org \
--cc=roy.pledge@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;
as well as URLs for NNTP newsgroup(s).