public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Paulo Marques <pmarques@grupopie.com>
Cc: Jesper Juhl <juhl-lkml@dif.dk>, Andrew Morton <akpm@osdl.org>,
	davem@davemloft.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/module.c has something to hide. (whitespace cleanup)
Date: Thu, 12 May 2005 00:56:57 +0200	[thread overview]
Message-ID: <20050511225657.GM6884@stusta.de> (raw)
In-Reply-To: <4281E78B.2030103@grupopie.com>

On Wed, May 11, 2005 at 12:07:55PM +0100, Paulo Marques wrote:
> Jesper Juhl wrote:
> >On Tue, 10 May 2005, Andrew Morton wrote:
> >
> >>Jesper Juhl <juhl-lkml@dif.dk> wrote:
> >>
> >>>[...]
> >>>Ohh, and I'd be submitting all the patches to you Andrew, not individual 
> >>>maintainers/authors..
> >>
> >>That should be OK - you can test that the .o files have the same `size'
> >>output before-and-after.
> >>
> >>[...]
> >
> >Ok, will do.
> 
> Just a small sugestion: do a sha (or md5sum, or whatever hash function 
> you prefer) to vmlinux before and after applying the patches.
> 
> If all is well, it shouldn't change (since this is just whitespace 
> cleanup), and it is a little more robust than just checking the size.


That's wrong.

vmlinux contains the date of the compilation.


> Paulo Marques - www.grupopie.com


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-05-11 22:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10 23:02 [PATCH] kernel/module.c has something to hide. (whitespace cleanup) Jesper Juhl
2005-05-10 23:16 ` Andrew Morton
2005-05-10 23:30   ` Jesper Juhl
     [not found]   ` <20050510.161907.116353193.davem@davemloft.net>
2005-05-11  0:02     ` Andrew Morton
2005-05-11  0:11       ` Jesper Juhl
2005-05-11  0:23         ` Andrew Morton
     [not found]       ` <20050510.170946.10291902.davem@davemloft.net>
2005-05-11  0:28         ` Jesper Juhl
2005-05-11  0:29           ` Andrew Morton
2005-05-11  0:38             ` Jesper Juhl
2005-05-11 11:07               ` Paulo Marques
2005-05-11 22:56                 ` Adrian Bunk [this message]
2005-05-12 12:16                   ` Paulo Marques
2005-05-12 13:36                     ` Paulo Marques
2005-05-12 17:26                       ` Jesper Juhl
2005-05-12 18:06                         ` Hugh Dickins
2005-05-11  1:01             ` Tom Duffy
2005-05-11  9:04               ` Adrian Bunk
     [not found] <42Mbg-Tq-25@gated-at.bofh.it>
     [not found] ` <42MXA-1zI-3@gated-at.bofh.it>
     [not found]   ` <42MXA-1zI-1@gated-at.bofh.it>
     [not found]     ` <42Nh3-1M8-17@gated-at.bofh.it>
     [not found]       ` <42Nh3-1M8-15@gated-at.bofh.it>
2005-05-11 23:47         ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-05-12  4:00           ` Nick Piggin
2005-05-12  5:16             ` Bodo Eggert
2005-05-12  8:41           ` Jesper Juhl
2005-05-12  8:47             ` Andrew Morton

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=20050511225657.GM6884@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=juhl-lkml@dif.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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