From: Alan Camus <albcamus@gmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: khaled MOHAMMED atteya <khaled.m.atteya@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: I hope to be kernel developer ,in i386 arch
Date: Sat, 29 Apr 2006 16:56:30 +0000 [thread overview]
Message-ID: <44539ABE.6050007@gmail.com> (raw)
In-Reply-To: <200604290536.k3T5arZs012263@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Sat, 29 Apr 2006 00:54:28 +0300, khaled MOHAMMED atteya said:
>
>> HELLO
>> I hope to be kernel developer ,in i386 arch.
>>
>
> Do you plan to be actively developing code in the arch/i386 tree, or are
> you just developing on systems that happen to be x86 boxes? The difference
> is crucial.
>
I want to be actively developing code in the arch/i386 or arch/x86_64
tree ... and plan to optimize the kernel for theses CPUs ... any advice
? thanks .
--alan
next prev parent reply other threads:[~2006-04-29 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 21:54 I hope to be kernel developer ,in i386 arch khaled MOHAMMED atteya
2006-04-29 4:43 ` Willy Tarreau
2006-04-29 5:36 ` Valdis.Kletnieks
2006-04-29 16:56 ` Alan Camus [this message]
2006-04-29 17:16 ` Jesper Juhl
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=44539ABE.6050007@gmail.com \
--to=albcamus@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=khaled.m.atteya@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox