All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Nelson <james4765@cwazy.co.uk>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Introduction...
Date: Mon, 07 Feb 2005 21:44:47 +0000	[thread overview]
Message-ID: <4207E14F.7080708@cwazy.co.uk> (raw)
In-Reply-To: <4206AF91.9315.17FD337@localhost>

[-- Attachment #1: Type: text/plain, Size: 986 bytes --]

Randy.Dunlap wrote:
> 
> In the absence of local cross-compiling, you could also submit your
> patch to the PLM tool at  http://www.osdl.org/plm-cgi/plm/
> and it will cross-compile the patch on 8 arches.  Latest -mm
> as example:
> https://www.osdl.org/plm-cgi/plm?module=patch_info&patch_id=4151
> 

Thanks for the pointer.  One of those things that is very useful to have available.

> If anyone is interested in stack reduction patches (besides me),
> I'm willing to help people understand what needs to be done,
> how to do it, etc., i.e., basically tutor people on this on this
> mailing list.  (See "make checkstack".)  Same applies to
> misused code section references (see "make buildcheck").
> 

Although I don't have infinite time to dedicate to it, I'm up for it.  I'm not 
very experienced, but am willing to flog my brain until I understand it.

After all, I came in here with the intent of learning kernel coding - gotta get 
beyond search-and-replace eventually ;)

Jim

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2005-02-07 21:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06 22:00 [KJ] Introduction Stephen Biggs
2005-02-07  2:51 ` Jim Nelson
2005-02-07  9:14 ` Stephen Biggs
2005-02-07 11:26 ` Jim Nelson
2005-02-07 13:14 ` Stephen Biggs
2005-02-07 15:35 ` Randy.Dunlap
2005-02-07 21:44 ` Jim Nelson [this message]
2005-02-12 22:05 ` Francois Romieu

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=4207E14F.7080708@cwazy.co.uk \
    --to=james4765@cwazy.co.uk \
    --cc=kernel-janitors@vger.kernel.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.