All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Amit Choudhary <amit2030@yahoo.com>
Cc: Vadim Lobanov <vlobanov@speakeasy.net>,
	Christoph Hellwig <hch@infradead.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] include/linux/slab.h: new KFREE() macro.
Date: Mon, 8 Jan 2007 09:09:26 +0000	[thread overview]
Message-ID: <20070108090926.GF17561@ftp.linux.org.uk> (raw)
In-Reply-To: <20070108084707.48375.qmail@web55605.mail.re4.yahoo.com>

On Mon, Jan 08, 2007 at 12:47:07AM -0800, Amit Choudhary wrote:
 
> Let's try to apply the same logic to my explanation:
> 
> KFREE() macro has __actually__ been used at atleast 1000 places in the kernel by atleast 50
> different people. Doesn't that lend enough credibility to what I am saying.

No.  Simple "it happens a lot of times" is _not_ enough to establish
credibility of "it should be done that way".  It is a good reason to
research the rationale in each case.
 
> People did something like this 1000 times: kfree(x), x = NULL. I simply proposed the KFREE() macro
> that does the same thing. Resistance to something that is already being done in the kernel. I
> really do not care whether it goes in the kernel or not. There are lots of other places where I
> can contribute. But I do not understand the resistance.
> 
> It is already being done in the kernel.

And each instance either has a reason for doing it that way or is useless
or is a bug.  Reasons, where they actually exist, very likely are not
uniform.

Blind copying of patterns without understanding what and why they are
doing is a Very Bad Thing(tm).  That's how the bugs are created and
propagated, BTW.

  reply	other threads:[~2007-01-08  9:09 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-07  8:46 [PATCH] include/linux/slab.h: new KFREE() macro Amit Choudhary
2007-01-07 10:24 ` Christoph Hellwig
2007-01-07 22:43   ` Amit Choudhary
2007-01-07 23:22     ` Vadim Lobanov
2007-01-08  0:02       ` Amit Choudhary
2007-01-08  2:35         ` Vadim Lobanov
2007-01-08  4:09           ` Amit Choudhary
2007-01-08  7:04             ` Vadim Lobanov
2007-01-08  7:29               ` Amit Choudhary
2007-01-08  8:15                 ` Vadim Lobanov
2007-01-08  8:47                   ` Amit Choudhary
2007-01-08  9:09                     ` Al Viro [this message]
2007-01-08  7:49     ` Hua Zhong
2007-01-08  8:00       ` Pekka Enberg
2007-01-08  8:31         ` Amit Choudhary
2007-01-08  8:37           ` Al Viro
2007-01-08  8:39           ` Sumit Narayan
2007-01-08  8:44             ` Robert P. J. Day
2007-01-08  8:56             ` Amit Choudhary
2007-01-08  8:45           ` Pekka Enberg
2007-01-08  9:06             ` Amit Choudhary
2007-01-08  9:26               ` Pekka Enberg
2007-01-08 22:43               ` Valdis.Kletnieks
2007-01-09 19:02                 ` Amit Choudhary
2007-01-09 19:19                   ` Randy Dunlap
2007-01-10  4:57                     ` Amit Choudhary
2007-01-09 22:57                   ` Valdis.Kletnieks
2007-01-10  0:00                     ` Amit Choudhary
2007-01-10  2:43                       ` Valdis.Kletnieks
2007-01-08 11:10           ` Jesper Juhl
2007-01-08  8:05       ` Amit Choudhary
2007-01-08  8:12         ` Al Viro
2007-01-08  8:57         ` Hua Zhong
  -- strict thread matches above, loose matches on Subject: below --
2007-07-23 17:55 Amit Choudhary
     [not found] <7ADs5-25a-11@gated-at.bofh.it>
     [not found] ` <7AP02-3l3-13@gated-at.bofh.it>
2007-01-08 18:29   ` Bodo Eggert
2007-01-01  0:17 Amit Choudhary
2007-01-01  3:01 ` Segher Boessenkool
2007-01-01 21:23 ` Pekka Enberg
2007-01-02  9:21   ` Christoph Hellwig

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=20070108090926.GF17561@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=amit2030@yahoo.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vlobanov@speakeasy.net \
    /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.