All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dick Streefland <dick@streefland.net>
To: Steven Rostedt <rostedt@goodmis.org>
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, 7 Oct 2009 10:41:35 +0200	[thread overview]
Message-ID: <20091007084135.GA5355@streefland.net> (raw)
In-Reply-To: <1254881503.1696.115.camel@gandalf.stny.rr.com>

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.

-- 
Dick

  reply	other threads:[~2009-10-07  8:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 20:35 [PATCH] kconfig: simplification of scripts/extract-ikconfig Dick Streefland
2009-10-07  2:11 ` Steven Rostedt
2009-10-07  8:41   ` Dick Streefland [this message]
2009-10-07 13:20     ` Steven Rostedt
  -- 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=20091007084135.GA5355@streefland.net \
    --to=dick@streefland.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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 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.