public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse•de>
To: Michal Marek <mmarek@suse•cz>
Cc: anil_ravindranath@pmc-sierra•com, mchehab@redhat•com,
	benh@kernel•crashing.org, x86@kernel•org, mac@melware•de,
	aacraid@adaptec•com, linux-mtd@lists•infradead.org,
	allan.stephens@windriver•com, hpa@zytor•com,
	netdev@vger•kernel.org, t.sailer@alumni•ethz.ch,
	gwingerde@gmail•com, IvDoorn@gmail•com, elf@buici•com,
	cluster-devel@redhat•com, ccaulfie@redhat•com, mingo@redhat•com,
	dougthompson@xmission•com, linux-media@vger•kernel.org,
	arnaud.giersch@free•fr, linux-kbuild@vger•kernel.org,
	teigland@redhat•com, tony.olech@elandigitalsystems•com,
	apw@canonical•com, linux-hams@vger•kernel.org,
	tglx@linutronix•de, swhiteho@redhat•com,
	linux-arm-kernel@lists•infradead.org, linux-edac@vger•kernel.org,
	jon.maloy@ericsson•com, linux-scsi@vger•kernel.org,
	linuxppc-dev@lists•ozlabs.org, linux-usb@vger•kernel.org,
	linux-wireless@vger•kernel.org, linux-kernel@vger•kernel.org,
	bluesmoke-
Subject: Re: [PATCH 00/34] Make kernel build deterministic
Date: Tue, 5 Apr 2011 08:49:18 -0700	[thread overview]
Message-ID: <20110405154918.GA31337@suse.de> (raw)
In-Reply-To: <1302015561-21047-1-git-send-email-mmarek@suse.cz>

On Tue, Apr 05, 2011 at 04:58:47PM +0200, Michal Marek wrote:
> 
> Hi,
> 
> this series makes it possible to build bit-identical kernel image and
> modules from identical sources. Of course the build is already
> deterministic in terms of behavior of the code, but the various
> timestamps embedded in the object files make it hard to compare two
> builds, for instance to verify that a makefile cleanup didn't
> accidentally change something. A prime example is /proc/config.gz, which
> has both a timestamp in the gzip header and a timestamp in the payload
> data. With this series applied, a script like this will produce
> identical kernels each time:

Very nice stuff.  Do you want to take the individual patches through one
of your trees, or do you mind if the subsystem maintainers take them
through theirs?

thanks,

greg k-h

  parent reply	other threads:[~2011-04-05 15:49 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 14:58 [PATCH 00/34] Make kernel build deterministic Michal Marek
2011-04-05 14:58 ` [PATCH 12/34] isdn/diva: Drop __TIME__ usage Michal Marek
2011-04-05 15:10   ` Armin Schindler
2011-04-05 15:37     ` Ben Hutchings
2011-04-05 16:07       ` Armin Schindler
2011-04-05 20:01         ` Sam Ravnborg
2011-04-05 19:17     ` Valdis.Kletnieks
2011-04-06  8:06       ` Michal Marek
2011-05-25 20:38     ` Michal Marek
2011-05-26  8:15       ` Armin Schindler
2011-05-26  8:29         ` Michal Marek
2011-04-05 14:59 ` [PATCH 15/34] baycom: " Michal Marek
     [not found]   ` <1302015780.4124.53.camel@xbox360.hq.axsem.com>
2011-05-25 15:23     ` Michal Marek
2011-04-05 14:59 ` [PATCH 17/34] hdlcdrv: " Michal Marek
2011-04-19 10:17   ` walter harms
2011-04-19 10:56     ` Michal Marek
     [not found]   ` <1302015790.4124.54.camel@xbox360.hq.axsem.com>
2011-05-25 15:24     ` Michal Marek
2011-04-05 14:59 ` [PATCH 18/34] wan/pc300: " Michal Marek
2011-05-25 20:43   ` Michal Marek
2011-05-25 20:44     ` David Miller
2011-04-05 14:59 ` [PATCH 19/34] rt2x00: " Michal Marek
2011-04-05 15:28   ` Gertjan van Wingerde
2011-04-05 18:37   ` Ivo Van Doorn
2011-04-05 14:59 ` [PATCH 28/34] atm: " Michal Marek
2011-05-25 20:49   ` Michal Marek
2011-05-25 21:39     ` David Miller
2011-04-05 14:59 ` [PATCH 29/34] tipc: " Michal Marek
2011-04-05 22:25   ` Paul Gortmaker
2011-04-05 15:49 ` Greg KH [this message]
2011-04-05 18:16   ` [PATCH 00/34] Make kernel build deterministic James Bottomley
2011-04-05 18:29     ` Mauro Carvalho Chehab
2011-04-05 18:44       ` Greg KH
2011-04-05 19:24   ` Artem Bityutskiy
2011-04-06  8:57     ` Ingo Molnar
2011-04-06  9:07     ` Michal Marek
2011-04-06  9:25       ` Artem Bityutskiy
2011-04-06  9:23   ` Michal Marek
2011-04-06  9:01 ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110405154918.GA31337@suse.de \
    --to=gregkh@suse$(echo .)de \
    --cc=IvDoorn@gmail$(echo .)com \
    --cc=aacraid@adaptec$(echo .)com \
    --cc=allan.stephens@windriver$(echo .)com \
    --cc=anil_ravindranath@pmc-sierra$(echo .)com \
    --cc=apw@canonical$(echo .)com \
    --cc=arnaud.giersch@free$(echo .)fr \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=ccaulfie@redhat$(echo .)com \
    --cc=cluster-devel@redhat$(echo .)com \
    --cc=dougthompson@xmission$(echo .)com \
    --cc=elf@buici$(echo .)com \
    --cc=gwingerde@gmail$(echo .)com \
    --cc=hpa@zytor$(echo .)com \
    --cc=jon.maloy@ericsson$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-edac@vger$(echo .)kernel.org \
    --cc=linux-hams@vger$(echo .)kernel.org \
    --cc=linux-kbuild@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-media@vger$(echo .)kernel.org \
    --cc=linux-mtd@lists$(echo .)infradead.org \
    --cc=linux-scsi@vger$(echo .)kernel.org \
    --cc=linux-usb@vger$(echo .)kernel.org \
    --cc=linux-wireless@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mac@melware$(echo .)de \
    --cc=mchehab@redhat$(echo .)com \
    --cc=mingo@redhat$(echo .)com \
    --cc=mmarek@suse$(echo .)cz \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=swhiteho@redhat$(echo .)com \
    --cc=t.sailer@alumni$(echo .)ethz.ch \
    --cc=teigland@redhat$(echo .)com \
    --cc=tglx@linutronix$(echo .)de \
    --cc=tony.olech@elandigitalsystems$(echo .)com \
    --cc=x86@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox