From: Gerrit Huizenga <gh@us.ibm.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
devenyga@mcmaster.ca, rml@tech9.net,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: PATCH: Replace current->state with set_current_state in 2.5.6 8
Date: Tue, 06 May 2003 19:01:27 -0700 [thread overview]
Message-ID: <E19DEFM-00022j-00@w-gerrit2> (raw)
In-Reply-To: Your message of Tue, 06 May 2003 18:24:56 PDT. <20030506182456.644b70d1.rddunlap@osdl.org>
On Tue, 06 May 2003 18:24:56 PDT, "Randy.Dunlap" wrote:
>
> On Tue, 6 May 2003 17:33:26 -0700 "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com> wrote:
>
> | However, I'd suggest to post this into the Kernel Janitors mailing list and
> | let one of the big guys there swipe it in.
> |
>
> Yes, the KJ list has already seen this patch and commented on some version
> of it.
> Then it needs some exposure, like living in -ac or -mm or -pick1,
> or at least some testing (everyday usage) by a few people, with reports
> from them.
>
> And I don't really want to review a 176 KB patch (although I did already
> look over most of it a few days ago). Do people want to take portions
> of it for review and then see about Alan merging it, e.g.?
Hmm. Has anyone considered a "Kernel Janitor's" tree? More specifically,
a patch set, much like -ac or -mm, with the current cleanups so they
can be tested, pulled, run through automated batch testing, etc.?
gerrit
next prev parent reply other threads:[~2003-05-07 1:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 0:33 Perez-Gonzalez, Inaky
2003-05-07 1:24 ` Randy.Dunlap
2003-05-07 2:01 ` Gerrit Huizenga [this message]
2003-05-07 2:07 ` Arnaldo Carvalho de Melo
2003-05-07 9:35 ` Paul P Komkoff Jr
2003-05-07 2:12 Perez-Gonzalez, Inaky
2003-05-07 3:20 ` Randy.Dunlap
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=E19DEFM-00022j-00@w-gerrit2 \
--to=gh@us.ibm.com \
--cc=devenyga@mcmaster.ca \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®