linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: laurentiu.tudor@nxp.com
Cc: stuyoder@gmail.com, devel@driverdev.osuosl.org, arnd@arndb.de,
	marc.zyngier@arm.com, Stuart Yoder <stuart.yoder@nxp.com>,
	roy.pledge@nxp.com, linux-kernel@vger.kernel.org, agraf@suse.de,
	catalin.horghidan@nxp.com, ioana.ciornei@nxp.com,
	Thomas Gleixner <tglx@linutronix.de>,
	leoyang.li@nxp.com, bharat.bhushan@nxp.com,
	Jason Cooper <jason@lakedaemon.net>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 10/10] staging: fsl-mc: move bus driver out of staging
Date: Tue, 13 Jun 2017 12:22:15 +0200	[thread overview]
Message-ID: <20170613102215.GA5866@kroah.com> (raw)
In-Reply-To: <20170608142855.10455-11-laurentiu.tudor@nxp.com>

On Thu, Jun 08, 2017 at 05:28:55PM +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

Why do you have so many different .h files?  You should only need 1
"external" one, and one "internal" one, right?  Can you please work on
cleaning that up first?

thanks,

greg k-h

  reply	other threads:[~2017-06-13 10:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 14:28 [PATCH v7 00/10] staging: fsl-mc: move bus driver out of staging laurentiu.tudor
2017-06-08 14:28 ` [PATCH v7 01/10] staging: fsl-mc: enclose macro params in parens laurentiu.tudor
2017-06-08 14:28 ` [PATCH v7 02/10] staging: fsl-mc: fix macros with possible side effects laurentiu.tudor
2017-06-13 10:12   ` Greg KH
2017-06-14 12:27     ` Laurentiu Tudor
2017-06-08 14:28 ` [PATCH v7 03/10] staging: fsl-mc: simplify couple of deallocations laurentiu.tudor
2017-06-08 14:28 ` [PATCH v7 04/10] staging: fsl-mc: drop a few useless #includes laurentiu.tudor
2017-06-08 14:28 ` [PATCH v7 05/10] staging: fsl-mc: remove extra blank line laurentiu.tudor
2017-06-08 14:28 ` [PATCH v7 06/10] staging: fsl-mc: drop unused forward declaration laurentiu.tudor
2017-06-08 14:28 ` [PATCH v7 07/10] staging: fsl-mc: add binding path to MAINTAINERS laurentiu.tudor
2017-06-08 14:28 ` [PATCH v7 08/10] staging: fsl-mc: drop reference to restool laurentiu.tudor
2017-06-08 14:28 ` [PATCH v7 09/10] staging: fsl-mc: add reference to mc-bus DT binding laurentiu.tudor
2017-06-08 14:28 ` [PATCH v7 10/10] staging: fsl-mc: move bus driver out of staging laurentiu.tudor
2017-06-13 10:22   ` Greg KH [this message]
2017-06-14 13:38     ` Laurentiu Tudor
2017-06-14 13:48       ` 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=20170613102215.GA5866@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=agraf@suse.de \
    --cc=arnd@arndb.de \
    --cc=bharat.bhushan@nxp.com \
    --cc=catalin.horghidan@nxp.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=ioana.ciornei@nxp.com \
    --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=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;
as well as URLs for NNTP newsgroup(s).