public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Damato <ice799@gmail.com>
To: linux-x86_64@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: x86: newb question - how to build everything which deps on x86
Date: Thu, 23 Oct 2008 23:25:08 -0700	[thread overview]
Message-ID: <49016A44.8040901@gmail.com> (raw)

Hi -

I am working on cleaning up include/asm-x86/desc_defs.h specifically 
replacing the fields a,b with more descriptive fields and including some 
other cleanups for using idts. I have some changes locally but as I was 
working on this I found that I had to make some changes to 
kernel/apm32.c kernel/cpu/common.c vmi and lguest (they all used the ->a 
and ->b fields directly).

There are probably more things in the kernel that depend on x86 and 
might break with my change. Is there some config flag I can flip to 
build all x86 related things? I tried a few patterns with grep, but I 
just want to make sure I don't break anyone's stuff.

Thanks,
Joe

             reply	other threads:[~2008-10-24  6:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24  6:25 Joe Damato [this message]
2008-10-24  9:12 ` x86: newb question - how to build everything which deps on x86 Chris Snook

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=49016A44.8040901@gmail.com \
    --to=ice799@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-x86_64@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