Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758936AbYFXKty (ORCPT ); Tue, 24 Jun 2008 06:49:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751405AbYFXKtq (ORCPT ); Tue, 24 Jun 2008 06:49:46 -0400 Received: from astoria.ccjclearline.com ([64.235.106.9]:59257 "EHLO astoria.ccjclearline.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750997AbYFXKtp (ORCPT ); Tue, 24 Jun 2008 06:49:45 -0400 Date: Tue, 24 Jun 2008 06:49:38 -0400 (EDT) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost.localdomain To: Linux Kernel Mailing List Subject: any reason for the continued hard-coding of "BUILD_CRAMDISK"? Message-ID: User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - astoria.ccjclearline.com X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - crashcourse.ca X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 852 Lines: 22 just curious as to whether there is still some value for the explicit definition of the BUILD_CRAMDISK macro in init/do_mounts_rd.c. that macro is unreferenced anywhere else in the tree, so it seems pointless to define and test a macro within the same source file. rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry: Have classroom, will lecture. http://crashcourse.ca Waterloo, Ontario, CANADA ======================================================================== -- 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/