Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751314Ab2HSEfN (ORCPT ); Sun, 19 Aug 2012 00:35:13 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:43385 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750742Ab2HSEfI (ORCPT ); Sun, 19 Aug 2012 00:35:08 -0400 X-Sasl-enc: LEs98QoPHdmJVqDGRUle5m4vfQjl9lYrvnGRjpb4ES5Z 1345350907 Date: Sun, 19 Aug 2012 01:35:04 -0300 From: Henrique de Moraes Holschuh To: "Yu, Fenghua" Cc: H Peter Anvin , Ingo Molnar , Thomas Gleixner , "Mallick, Asit K" , Tigran Aivazian , Andreas Herrmann , Borislav Petkov , linux-kernel , x86 Subject: Re: [PATCH 02/11] x86/lib/cpio.c: Find cpio data by its file name Message-ID: <20120819043504.GA9773@khazad-dum.debian.net> References: <1345277729-8399-1-git-send-email-fenghua.yu@intel.com> <1345277729-8399-3-git-send-email-fenghua.yu@intel.com> <20120818221252.GA32120@khazad-dum.debian.net> <3E5A0FA7E9CA944F9D5414FEC6C712200778794E@ORSMSX105.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E5A0FA7E9CA944F9D5414FEC6C712200778794E@ORSMSX105.amr.corp.intel.com> X-GPG-Fingerprint: 1024D/1CDB0FE3 5422 5C61 F6B7 06FB 7E04 3738 EE25 DE3F 1CDB 0FE3 User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1309 Lines: 30 On Sat, 18 Aug 2012, Yu, Fenghua wrote: > > From: Henrique de Moraes Holschuh [mailto:hmh@hmh.eng.br] On Sat, 18 Aug > > 2012, Fenghua Yu wrote: > > > Given a file's name, find its starting point in a cpio formated area. > > This will > > > be used to find microcode in combined initrd image. But this function > > is > > > generic and could be used in other places. > > > > Shouldn't this (very useful) feature get its own documentation in > > Documentation/ ? > > Yes, I can document the feature. And if it's generic and useful, this > function could be put in generic kernel instead of in x86 arch. It is useful to override/fix all sort of critical firmware-provided tables, for example. ACPI table overrides should use this new cpio-based scheme as well, and I recall someone wrote something about device tree overrides in a past thread... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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/