Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 16 Nov 2002 00:07:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 16 Nov 2002 00:07:03 -0500 Received: from sccrmhc02.attbi.com ([204.127.202.62]:42741 "EHLO sccrmhc02.attbi.com") by vger.kernel.org with ESMTP id ; Sat, 16 Nov 2002 00:07:02 -0500 Message-ID: <3DD5D93F.8070505@kegel.com> Date: Fri, 15 Nov 2002 21:35:59 -0800 From: Dan Kegel User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830 X-Accept-Language: de-de, en MIME-Version: 1.0 To: john slee , Linux Kernel Mailing List Subject: Why can't Johnny compile? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1180 Lines: 24 john slee wrote: > On Thu, Nov 14, 2002 at 10:58:09PM -0500, Patrick Finnegan wrote: >> It'd be nice if people simply tried compiling a patched kernel (all >> affected modules) before they submitted the patch, I'm betting you'd catch >> a lot of typos. Also, compiling _everything_, even as a module, at >> least once before sumbitting the patch would probably help. > > thats fine if there is an all-compiling kernel release out there. right > now 2.5-bk is far from it. last i checked allmodconfig (a couple of > days ago) there was major breakage all over llc, scsi, video, sound, ... > which kinda masks any breakages you might have introduced. Hrmph. Y'know, maybe it's time for us to collectively put our feet down, get 2.5-linus to the point where everything compiles, and keep it there. After all, we are supposedly trying to *stabilize* 2.5. It isn't stable if it doesn't compile... - Dan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/