mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: gorcunov@gmail.com, geert@linux-m68k.org, zippel@linux-m68k.org,
	schwab@suse.de, linux-kernel@vger.kernel.org,
	linux-m68k@vger.kernel.org
Subject: Re: [PATCH] init - fix building bug and potential buffer overflow
Date: Thu, 15 May 2008 18:47:27 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0805151844440.2941@woody.linux-foundation.org> (raw)
In-Reply-To: <20080515144554.7b759b3c.akpm@linux-foundation.org>



On Thu, 15 May 2008, Andrew Morton wrote:
> 
> this, basically:
> 
> >  init/main.c |   78 +++++++++++++++++++++++++++++++----------------------------
> >  1 files changed, 41 insertions(+), 37 deletions(-)
> 
> the dont-mix-bugfixes-and-cleanups mantra.

Sure. I committed them as two separate things.

The point *I* had was that we don't make source code uglier for arbitrary 
reasons. The checkpatch.pl script shouldn't be powerful enough that we do 
uglier source code and break arbitrary rules just to make that script 
happy.

So either we should sy "screw the script, it's wrong", or we should just 
not fix the bug. Or we should say "ok, I can write even _better_ source 
code, and fix the bug, make the source look nicer _and_ not piss off the 
script too".

> > Would somebody please want to move that cast into the macro (or better 
> > yet, make it an inline function that takes a 'void *'), and remove all the 
> > casts from the callers?
> 
> Would be nice.

So I did that too.

		Linus

  parent reply	other threads:[~2008-05-16  1:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 15:44 Cyrill Gorcunov
2008-05-15 17:58 ` Andrew Morton
2008-05-15 18:05   ` Cyrill Gorcunov
2008-05-15 19:47     ` Geert Uytterhoeven
2008-05-15 20:22       ` Cyrill Gorcunov
2008-05-15 20:49         ` Andrew Morton
2008-05-15 21:15           ` Linus Torvalds
2008-05-15 21:45             ` Andrew Morton
2008-05-15 23:41               ` [PATCH] Add a void * alternative to print_fn_descriptor_symbol() Abhijit Menon-Sen
2008-05-16  1:47               ` Linus Torvalds [this message]
2008-05-15 22:44             ` [PATCH] init - fix building bug and potential buffer overflow Rene Herman
2008-05-16  3:29           ` Cyrill Gorcunov
2008-05-16  4:17             ` Cyrill Gorcunov
2008-05-16  7:00           ` Geert Uytterhoeven

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=alpine.LFD.1.10.0805151844440.2941@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=gorcunov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schwab@suse.de \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®