All of lore.kernel.org
 help / color / mirror / Atom feed
From: ablacktshirt@gmail.com (walkerlala)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Can I just remove code of other architectures and get a clean X86 source
Date: Thu, 12 May 2016 20:50:41 +0800	[thread overview]
Message-ID: <57347C21.5030909@gmail.com> (raw)

     Hi everyone.
     I am just reading the kernel code, adding some code to make it 
pause and print some text and then interact with it a little bit. I have 
compile the kernel successfully and run the kernel in QEMU. It did 
work.Nice.
     But, when I reading the source, I found that there are just too 
many files there, which make it hard for me to manage. With so many 
files, It's hard to change directories, read and modified and still 
remember what you are doing (so many files with the same/similar name).
     I know that's because Linux support many architectures, and that 's 
the reason why there are so many folders under the 'arch' directory of 
the source code.
     So, I wonder, as I only want the source for x86 device, can I 
simply remove that source files which are unrelated to x86 and still 
make the kernel work as normal? I mean, can I just remove all the 
directory under 'arch' except 'x86-64' ? Also, are there any other files 
that I can safely removed and won't hurt the kernel ?
     Thanks in advance.
     (btw, I don't know whether this question is asked before. I google 
it but find nothing related. If it's duplicated, please give me some 
pointer to the mailing list where this topic located )

             reply	other threads:[~2016-05-12 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 12:50 walkerlala [this message]
2016-05-12 13:17 ` Can I just remove code of other architectures and get a clean X86 source Carlo Caione

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=57347C21.5030909@gmail.com \
    --to=ablacktshirt@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.