Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 20 Apr 2001 09:21:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 20 Apr 2001 09:20:52 -0400 Received: from router-100M.swansea.linux.org.uk ([194.168.151.17]:9221 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Fri, 20 Apr 2001 09:20:36 -0400 Subject: Re: [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? To: esr@thyrsus.com Date: Fri, 20 Apr 2001 14:08:25 +0100 (BST) Cc: willy@ldl.fc.hp.com (Matthew Wilcox), linux-kernel@vger.kernel.org, parisc-linux@parisc-linux.org In-Reply-To: <20010419230009.A32500@thyrsus.com> from "Eric S. Raymond" at Apr 19, 2001 11:00:09 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > What is the right procedure for doing changes like this? Is "don't > touch that tree" a permanent condition, or am I going to get a chance > to clean up the global CONFIG_ namespace after your next merge-down? Feeding arch related stuff to the architecture maintainers. > That's the main thing I'm after right now -- I want to cut down on > the false positives in my orphaned-symbol reports so that the actual > bugs will stand out. Teach it to read a 'symbolstoignore' file. Part of the problem you are hitting right now is that most architectures are not yet fully in sync with 2.4 nor likely to all be for another few iterations. - 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/