All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Martyn Welch <martyn.welch@ge.com>
Cc: Samuel Iglesias Gonsalvez <siglesias@igalia.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] Staging: ipack: move the devices source line in Kconfig file
Date: Fri, 11 May 2012 07:58:56 -0700	[thread overview]
Message-ID: <20120511145856.GG5958@kroah.com> (raw)
In-Reply-To: <4FACF22C.1050304@ge.com>

On Fri, May 11, 2012 at 12:04:12PM +0100, Martyn Welch wrote:
> On 11/05/12 09:17, Samuel Iglesias Gonsalvez wrote:
> > Maintain the proper order of definitions in Kconfig following the time order of
> > the commits.
> > 
> 
> This could probably be rolled up into patch 1.

It could, but this is fine, they do two different things.

thanks,

greg k-h

  reply	other threads:[~2012-05-11 14:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11  8:17 [PATCH 1/7] Staging: move the position of the ipack source line in Kconfig Samuel Iglesias Gonsalvez
2012-05-11  8:17 ` [PATCH 2/7] Staging: ipack: move the devices source line in Kconfig file Samuel Iglesias Gonsalvez
2012-05-11 11:04   ` Martyn Welch
2012-05-11 14:58     ` Greg Kroah-Hartman [this message]
2012-05-11  8:17 ` [PATCH 3/7] Staging: ipack: add contact email in TODO file Samuel Iglesias Gonsalvez
2012-05-11  8:17 ` [PATCH 4/7] Staging: ipack: change the licence to explicitly GPLv2 Samuel Iglesias Gonsalvez
2012-05-11  8:17 ` [PATCH 5/7] Staging: ipack/bridges/tpci200: " Samuel Iglesias Gonsalvez
2012-05-11 11:04   ` Martyn Welch
2012-05-11  8:17 ` [PATCH 6/7] Staging: ipack/devices/ipoctal: " Samuel Iglesias Gonsalvez
2012-05-11 11:05   ` Martyn Welch
2012-05-11 14:58     ` Greg Kroah-Hartman
2012-05-11  8:17 ` [PATCH 7/7] Staging ipack: added more info in Kconfig's help about ipack Samuel Iglesias Gonsalvez

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=20120511145856.GG5958@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martyn.welch@ge.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.