public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Samuel Iglesias Gonsalvez <siglesias@igalia.com>
Cc: devel@driverdev.osuosl.org, jens.taprogge@taprogge.org,
	linux-kernel@vger.kernel.org,
	industrypack-devel@lists.sourceforge.net
Subject: Re: [PATCH] ipack: move header files to include/linux
Date: Fri, 16 Nov 2012 09:44:10 -0800	[thread overview]
Message-ID: <20121116174410.GA2143@kroah.com> (raw)
In-Reply-To: <1353087276-4861-1-git-send-email-siglesias@igalia.com>

On Fri, Nov 16, 2012 at 06:34:36PM +0100, Samuel Iglesias Gonsalvez wrote:
> Move ipack header files to include/linux/ directory where they belong to.
> 
> Signed-off-by: Samuel Iglesias Gonsalvez <siglesias@igalia.com>
> ---
>  drivers/ipack/carriers/tpci200.h |    3 +-
>  drivers/ipack/devices/ipoctal.c  |    2 +-
>  drivers/ipack/ipack.c            |    2 +-
>  drivers/ipack/ipack.h            |  215 --------------------------------------
>  drivers/ipack/ipack_ids.h        |   32 ------
>  include/linux/ipack.h            |  214 +++++++++++++++++++++++++++++++++++++
>  include/linux/ipack_ids.h        |   32 ++++++
>  7 files changed, 249 insertions(+), 251 deletions(-)
>  delete mode 100644 drivers/ipack/ipack.h
>  delete mode 100644 drivers/ipack/ipack_ids.h
>  create mode 100644 include/linux/ipack.h
>  create mode 100644 include/linux/ipack_ids.h

Can you send me a patch in -M format, that just shows the files moving
next time?

Also, do we really need the ipack_ids.h file in include/linux?  It looks
like only the core ipack code cares about the values there, right?

thanks,

greg k-h

  reply	other threads:[~2012-11-16 17:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 17:34 [PATCH] ipack: move header files to include/linux Samuel Iglesias Gonsalvez
2012-11-16 17:44 ` Greg Kroah-Hartman [this message]
2012-11-16 17:48   ` Samuel Iglesias Gonsálvez
2012-11-16 17:53     ` Samuel Iglesias Gonsálvez
2012-11-16 18:00       ` Greg Kroah-Hartman
2012-11-16 18:08 ` Joe Perches
2012-11-16 18:14   ` Samuel Iglesias Gonsálvez
2012-11-16 19:01     ` Joe Perches
2012-11-16 19:04     ` Greg Kroah-Hartman

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=20121116174410.GA2143@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=industrypack-devel@lists.sourceforge.net \
    --cc=jens.taprogge@taprogge.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=siglesias@igalia.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