From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: "Ben Dooks" <ben@simtec.co.uk>,
"Vincent Sanders" <vince@simtec.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] mfd/sm501.c: #if 0 unused functions
Date: Sun, 13 Apr 2008 21:34:24 +0200 [thread overview]
Message-ID: <9a8748490804131234v26fefe9dp633fd0509b0fff6@mail.gmail.com> (raw)
In-Reply-To: <20080413192420.GC21204@cs181133002.pp.htv.fi>
On 13/04/2008, Adrian Bunk <bunk@kernel.org> wrote:
> On Sun, Apr 13, 2008 at 09:08:31PM +0200, Jesper Juhl wrote:
> > On 13/04/2008, Adrian Bunk <bunk@kernel.org> wrote:
> > > On Sun, Apr 13, 2008 at 08:55:21PM +0200, Jesper Juhl wrote:
> > > > On 13/04/2008, Adrian Bunk <bunk@kernel.org> wrote:
> > > > > This patch #if 0's the following unused functions:
> > > > > - sm501_find_clock()
> > > > > - sm501_gpio_get()
> > > > > - sm501_gpio_set()
> > > > >
> > > >
> > > > Hi Adrian,
> > > >
> > > > I know we've discussed this before, but I have to comment on this once more.
> > > >
> > > > Why is it that you seem to prefer adding '#if 0' around blocks of
> > > > unused code instead of removing it outright?
> > >
> > > >...
> > >
> > > When I removed unused code outright some people complained that they
> > > plan to use it tomorrow or in the next millenium or whenever.
> > >
> > > When I #if 0 it other people complain that I should remove it outright.
> > >
> > > So whatever I do, there's always someone complaining. ;-)
> > >
> > > In this case the code looks as if it might get used at some point in the
> > > future.
> > >
> > > But if a maintainer tells me to resend a patch with the code removed
> > > instead of #if 0'ed I'm always glad to do this.
> > >
> > But, you are completely ignoring the case of "the code is unused, but
> > will probably be used soon, so I'll just leave it alone and avoid the
> > churn". Why? What's the point of commenting it out now and then
> > enabling it again in a month or two - isn't that just pointless churn?
>
> >...
>
> It's unused since more than one year, so chances are it won't get used
> in a month or two.
>
Then I really don't see why you chose the '#if 0' option. In that case
it would seem to me that either "leave it alone, don't submit a patch"
or "submit a patch to remove it outright" would both be more
preferable options.
> As I said, if a maintainer wants me to remove it outright I'll be glad
> to do so.
>
I don't doubt that.
> And as I said, no matter whatever I do, there's always someone
> complaining...
>
Please don't see my comments as complaints. They are not intended as
such. I'm merely currious why we keep adding all these '#if 0's since
I don't see the point and I can just see them piling up into some huge
janitorial mountain from hell to be tackled some time in the future by
whomever is masochistic enough to try ;-)
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2008-04-13 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 18:15 Adrian Bunk
2008-04-13 18:55 ` Jesper Juhl
2008-04-13 19:03 ` Adrian Bunk
2008-04-13 19:08 ` Jesper Juhl
2008-04-13 19:24 ` Adrian Bunk
2008-04-13 19:32 ` Dmitri Vorobiev
2008-04-13 19:43 ` Adrian Bunk
2008-04-13 19:34 ` Jesper Juhl [this message]
2008-04-13 19:47 ` Adrian Bunk
2008-04-13 19:53 ` Jesper Juhl
2008-05-05 18:25 Adrian Bunk
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=9a8748490804131234v26fefe9dp633fd0509b0fff6@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=ben@simtec.co.uk \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vince@simtec.co.uk \
/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®