From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752716Ab2GSOmY (ORCPT ); Thu, 19 Jul 2012 10:42:24 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:27981 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752498Ab2GSOmT (ORCPT ); Thu, 19 Jul 2012 10:42:19 -0400 X-Authority-Analysis: v=2.0 cv=ZuBv2qHG c=1 sm=0 a=s5Htg7xnQOKvHEu9STBOug==:17 a=OpT9cpI26MMA:10 a=wom5GMh1gUkA:10 a=0wpEoyeJZggA:10 a=5SG0PmZfjMsA:10 a=kj9zAlcOel0A:10 a=meVymXHHAAAA:8 a=nhfWb_NetKUeJCV5-g0A:9 a=CjuIK1q_8ugA:10 a=s5Htg7xnQOKvHEu9STBOug==:117 X-Cloudmark-Score: 0 X-Originating-IP: 72.230.195.127 Date: Thu, 19 Jul 2012 10:42:17 -0400 From: Steven Rostedt To: Borislav Petkov Cc: Cyrill Gorcunov , Pekka Enberg , richard -rw- weinberger , "Myklebust, Trond" , Linus Torvalds , Dave Jones , Greg Kroah-Hartman , Ubuntu Kernel Team , Debian Kernel Team , OpenSUSE Kernel Team , Linux Kernel Mailing List , Ingo Molnar , Sasha Levin , Asias He Subject: Re: [opensuse-kernel] Re: [RFC] Simplifying kernel configuration for distro issues Message-ID: <20120719144217.GC16873@home.goodmis.org> References: <1342212885.25704.4.camel@lade.trondhjem.org> <20120714103716.GD26559@liondog.tnic> <20120714124332.GA4093@moon> <20120714174827.GA13319@aftab.osrc.amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120714174827.GA13319@aftab.osrc.amd.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jul 14, 2012 at 07:48:27PM +0200, Borislav Petkov wrote: > > Let's have an example: when I have to build upstream on a distro here, > I take the distro config and use it despite that it takes a long time > to build since everything is module - it is still better for me to > wait that one time instead of doing a dozen of trial and errors after > forgetting a config option each time. This is where 'make localmodconfig' does help. It can remove a lot of modules for you. And I just recently fixed a bug in the tool that it now removes even more modules (The fix is in linux-next). Also, if you are building on another box than what the kernel is for, you can go to that box and run 'lsmod > /tmp/lsmod'. Copy that file to the build machine (into /tmp/lsmod), and then run 'make LSMOD=/tmp/lsmod localmodconfig', and this will remove the modules not used by the target box. -- Steve