All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andries Brouwer <aebr@win.tue.nl>,
	Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] __init in mm/slab.c
Date: Sun, 14 Nov 2004 19:58:23 +0100	[thread overview]
Message-ID: <4197AACF.9090303@colorfullife.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0411141823460.2216@ppc970.osdl.org>

Linus Torvalds wrote:

>On Sun, 14 Nov 2004, Andries Brouwer wrote:
>  
>
>>So yesterday's series of __init patches is not because there were
>>bugs, but because it is desirable to have the situation where
>>static inspection of the object code shows absence of references
>>to .init stuff. Much better than having to reason that there is
>>a reference but that it will not be used.
>>    
>>
>
>And I agree heartily with this. I love static checking (after all, that's 
>all that sparse does), and if you can make sure that there is one less 
>thing to be worried about, all the better.
>
>Of course, another option to just removing/fixing the __init is to have 
>some way to let the static checker know things are ok, but in this case, 
>especially with fairly small data structures, it seems much easier to just 
>make the checker happy.
>
>  
>
I agree, but a comment would have been nice. Now there are two identical 
structures that are used for the same purpose, one __init, one not __init.

I'd bet that sooner or later someone will ask why.

--
    Manfred

  reply	other threads:[~2004-11-14 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1CTDXF-0006mU-00@bkwatch.colorfullife.com>
2004-11-14  8:18 ` [PATCH] __init in mm/slab.c Manfred Spraul
2004-11-14 11:15   ` Andries Brouwer
2004-11-15  2:26     ` Linus Torvalds
2004-11-14 18:58       ` Manfred Spraul [this message]
2004-11-14  1:27 Andries Brouwer

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=4197AACF.9090303@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=aebr@win.tue.nl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.