linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bogdan Purcareata <bogdan.purcareata@nxp.com>
To: gregkh@linuxfoundation.org, laurentiu.tudor@nxp.com,
	ruxandra.radulescu@nxp.com
Cc: devel@driverdev.osuosl.org, stuyoder@gmail.com,
	horia.geanta@nxp.com, roy.pledge@nxp.com, ioana.ciornei@nxp.com,
	linux-kernel@vger.kernel.org, nipun.gupta@nxp.com,
	Bogdan Purcareata <bogdan.purcareata@nxp.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] staging: fsl-mc: Move DPBP and DPCON out of staging
Date: Fri,  2 Mar 2018 04:23:57 -0600	[thread overview]
Message-ID: <20180302102359.16979-1-bogdan.purcareata@nxp.com> (raw)

Previous submission: https://lkml.org/lkml/2018/3/1/733

Commit 6bd067c48ef ("staging: fsl-mc: Move core bus out of staging")
moves the fsl-mc bus driver infrastructure out of staging to
drivers/bus/fsl-mc. The next step is moving a couple of tightly
connected DPAA2 objects - DPBP (Data Path Buffer Pool) and DPCON
(Data Path Concentrator).

The patches handle moving out the mentioned objects, one at a time.

v1 -> v2:
- previous cleanup patch already applied, so removed from patchset
- properly refactor #include line (Laurentiu)

Bogdan Purcareata (2):
  staging: fsl-mc: Move DPBP out of staging
  staging: fsl-mc: Move DPCON out of staging

 drivers/bus/fsl-mc/Makefile                        |   2 +
 drivers/{staging/fsl-mc/bus => bus/fsl-mc}/dpbp.c  |   4 +-
 drivers/{staging/fsl-mc/bus => bus/fsl-mc}/dpcon.c |   4 +-
 drivers/bus/fsl-mc/fsl-mc-private.h                |  87 +++++++++++++++++
 drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.h     |   3 +-
 drivers/staging/fsl-mc/bus/Makefile                |   2 -
 drivers/staging/fsl-mc/bus/dpbp-cmd.h              |  44 ---------
 drivers/staging/fsl-mc/bus/dpcon-cmd.h             |  53 ----------
 drivers/staging/fsl-mc/include/dpbp.h              |  53 ----------
 drivers/staging/fsl-mc/include/dpcon.h             |  79 ---------------
 include/linux/fsl/mc.h                             | 108 +++++++++++++++++++++
 11 files changed, 202 insertions(+), 237 deletions(-)
 rename drivers/{staging/fsl-mc/bus => bus/fsl-mc}/dpbp.c (98%)
 rename drivers/{staging/fsl-mc/bus => bus/fsl-mc}/dpcon.c (99%)
 delete mode 100644 drivers/staging/fsl-mc/bus/dpbp-cmd.h
 delete mode 100644 drivers/staging/fsl-mc/bus/dpcon-cmd.h
 delete mode 100644 drivers/staging/fsl-mc/include/dpbp.h
 delete mode 100644 drivers/staging/fsl-mc/include/dpcon.h

-- 
2.7.4

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

             reply	other threads:[~2018-03-02 10:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 10:23 Bogdan Purcareata [this message]
2018-03-02 10:23 ` [PATCH v2 1/2] staging: fsl-mc: Move DPBP out of staging Bogdan Purcareata
2018-03-02 10:23 ` [PATCH v2 2/2] staging: fsl-mc: Move DPCON " Bogdan Purcareata

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=20180302102359.16979-1-bogdan.purcareata@nxp.com \
    --to=bogdan.purcareata@nxp.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=horia.geanta@nxp.com \
    --cc=ioana.ciornei@nxp.com \
    --cc=laurentiu.tudor@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nipun.gupta@nxp.com \
    --cc=roy.pledge@nxp.com \
    --cc=ruxandra.radulescu@nxp.com \
    --cc=stuyoder@gmail.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;
as well as URLs for NNTP newsgroup(s).