From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LfauQ-0004ty-EP for garchives@archives.gentoo.org; Fri, 06 Mar 2009 14:20:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 93E83E011D; Fri, 6 Mar 2009 14:20:16 +0000 (UTC) Received: from mail.evildaystar.net (unknown [96.237.185.140]) by pigeon.gentoo.org (Postfix) with ESMTP id 75BF4E011D for ; Fri, 6 Mar 2009 14:20:16 +0000 (UTC) Received: from Inbox (28.sub-75-192-174.myvzw.com [75.192.174.28]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.evildaystar.net (Postfix) with ESMTPSA id D4717CC2BB for ; Fri, 6 Mar 2009 09:18:49 -0500 (EST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-admin@lists.gentoo.org Reply-to: gentoo-admin@lists.gentoo.org MIME-Version: 1.0 content-class: From: Two_Tone Subject: RE: [gentoo-admin] Making changes to a statically build driver Date: Fri, 6 Mar 2009 09:20:28 -0500 Importance: normal X-Priority: 3 To: Content-Type: multipart/alternative; boundary="_DC0AB8A7-FB4E-CA66-5A4E-A1E454631765_" Message-Id: <20090306141849.D4717CC2BB@mail.evildaystar.net> X-Archives-Salt: ad940aac-f021-4f1c-a03f-2753d447319f X-Archives-Hash: 150b2397f1ba7dcbb8ca9a7279c76ca4 --_DC0AB8A7-FB4E-CA66-5A4E-A1E454631765_ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" You could md5 hash the old and new kernel. If the hash is different then c= hanges were made. -----Original Message----- From: Ezra Taylor Sent: Thursday, Mar 5 2009 6:16 PM To: gentoo-user@lists.gentoo.org; gentoo-admin@lists.gentoo.org Subject: [gentoo-admin] Making changes to a statically build driver Hello all: =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 I made some changes to the e1000= kernel driver.=A0 I then recompiled the kernel without any issue.=A0 How c= an I tell if the change actually went through?=A0 Again, this driver has be= en statically built into the kernel.=A0 Is there a way to test that a chang= e went through without have to setup a test environment? --=20 Ezra Taylor --_DC0AB8A7-FB4E-CA66-5A4E-A1E454631765_ Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1" You could md5 hash the old and new kernel. If the ha= sh is different then changes were made.

From: Ezra Taylor <= ;ezra.taylor@gmail.com>
Sent: Thursday, Mar 5 2009 6:16 PM<= br>To: = gentoo-user@lists.gentoo.org; gentoo-admin@lists.gentoo.org
Subject: = [gentoo-admin] Making changes to a statically build driver
Hello all:
          =      I made some changes to the e1000 kernel driver.&nb= sp; I then recompiled the kernel without any issue.  How can I tell if= the change actually went through?  Again, this driver has been static= ally built into the kernel.  Is there a way to test that a change went= through without have to setup a test environment?

-- =
Ezra Taylor
= --_DC0AB8A7-FB4E-CA66-5A4E-A1E454631765_--