mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Dick Streefland <dick@streefland.net>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] kconfig: simplification of scripts/extract-ikconfig
Date: Wed, 07 Oct 2009 09:20:47 -0400	[thread overview]
Message-ID: <1254921647.1696.135.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20091007084135.GA5355@streefland.net>

On Wed, 2009-10-07 at 10:41 +0200, Dick Streefland wrote:
> On Tuesday 2009-10-06 22:11, Steven Rostedt wrote:
> | Now the question is, is this something that we should try to get into
> | the 32 release, or let this version go through linux-next for another
> | release?
> 
> I don't have a strong preference, as long as it gets into the kernel
> tree in the end. I realize that it is a bit late in the 32 release
> cycle, but on the other hand this script is not used in the kernel
> build process.

I'm sure it is fine, but since we are after the merge window, I'll push
this off to linux-next.

Thanks,

-- Steve



  reply	other threads:[~2009-10-07 13:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 20:35 Dick Streefland
2009-10-07  2:11 ` Steven Rostedt
2009-10-07  8:41   ` Dick Streefland
2009-10-07 13:20     ` Steven Rostedt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-23 22:52 Dick Streefland
2009-06-24  2:15 ` Amerigo Wang
2009-06-24 11:46   ` Dick Streefland
2009-06-24 13:31     ` Dick Streefland
2009-06-29  2:51       ` Amerigo Wang
2009-06-29 11:36         ` Dick Streefland
2009-07-09  2:38           ` Amerigo Wang
2009-07-09  8:26             ` Dick Streefland
2009-07-10  7:55               ` Amerigo Wang
2009-07-10  9:54                 ` Dick Streefland
2009-07-17 21:17                   ` Sam Ravnborg
2009-07-17 23:08                     ` Dick Streefland
2009-07-18  7:06                       ` Sam Ravnborg

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=1254921647.1696.135.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=dick@streefland.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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
all inboxes | Powered by JetHome®