public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
	Suresh Siddha <suresh.b.siddha@intel.com>
Subject: [PATCH 0/5] x86: Improve defconfigs for use on current systems
Date: Sun, 2 Sep 2012 22:20:48 -0700	[thread overview]
Message-ID: <cover.1346649518.git.josh@joshtriplett.org> (raw)

After repeatedly going through the cycle of building a "make defconfig" kernel,
trying to boot it, getting a kernel panic, turning on ext4, and rebuilding, I
figured I'd actually get the defconfigs fixed to work on modern systems with
ext4 root filesystems.  Patch 2 of this patch series does exactly that.
Hopefully this will prove uncontroversial.

To avoid extraneous noise in patch 2, I first updated the defconfigs to match
the current results of "make defconfig && make savedefconfig", resulting in
patch 1.

Finally, while reviewing the defconfigs, I also ran into a few other random
things to clean up, resulting in patches 3-5.  Patch 3 disables some library
code that only exists to support out-of-tree modules (in-tree modules properly
depend on it); patch 4 disables initrd support (in favor of initramfs); patch 5
disables a special-purpose test module that represents the one and only module
built by default.  These seem reasonable to me, but if anyone finds one of
these three changes objectionable, please feel free to drop that change.  I
primarily care about getting patches 1-2 merged, to avoid a very common
annoyance.

Josh Triplett (5):
  x86: Update defconfigs to current results of "make savedefconfig"
  x86: Switch to ext4 in defconfigs
  x86: Disable CONFIG_CRC_T10DIF in defconfigs
  x86, defconfig: Turn off CONFIG_BLK_DEV_RAM
  x86: Turn off DEBUG_NX_TEST module in defconfigs

 arch/x86/configs/i386_defconfig   |   23 +++++++----------------
 arch/x86/configs/x86_64_defconfig |   23 +++++++----------------
 2 files changed, 14 insertions(+), 32 deletions(-)

-- 
1.7.10.4


             reply	other threads:[~2012-09-03  5:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-03  5:20 Josh Triplett [this message]
2012-09-03  5:20 ` [PATCH 1/5] x86: Update defconfigs to current results of "make savedefconfig" Josh Triplett
2012-09-05 10:49   ` [tip:x86/build] x86/Kconfig: " tip-bot for Josh Triplett
2012-09-03  5:21 ` [PATCH 2/5] x86: Switch to ext4 in defconfigs Josh Triplett
2012-09-05 10:50   ` [tip:x86/build] x86/Kconfig: " tip-bot for Josh Triplett
2012-09-03  5:21 ` [PATCH 3/5] x86: Disable CONFIG_CRC_T10DIF " Josh Triplett
2012-09-05 10:51   ` [tip:x86/build] x86/Kconfig: " tip-bot for Josh Triplett
2012-09-03  5:21 ` [PATCH 4/5] x86, defconfig: Turn off CONFIG_BLK_DEV_RAM Josh Triplett
2012-09-05 10:52   ` [tip:x86/build] x86/Kconfig: " tip-bot for Josh Triplett
2012-09-03  5:21 ` [PATCH 5/5] x86: Turn off DEBUG_NX_TEST module in defconfigs Josh Triplett
2012-09-05 10:53   ` [tip:x86/build] x86/Kconfig: " tip-bot for Josh Triplett

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=cover.1346649518.git.josh@joshtriplett.org \
    --to=josh@joshtriplett.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rdunlap@xenotime.net \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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