From: Willy Tarreau <willy@w.ods.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.30-rc2
Date: Sat, 26 Mar 2005 13:27:06 +0100 [thread overview]
Message-ID: <20050326122706.GA14756@alpha.home.local> (raw)
In-Reply-To: <1111837493.8042.2.camel@laptopd505.fenrus.org>
On Sat, Mar 26, 2005 at 12:44:53PM +0100, Arjan van de Ven wrote:
> On Sat, 2005-03-26 at 12:22 +0100, Willy Tarreau wrote:
> > Marcelo,
> >
> > here's a patch from Dave Jones, which is already in 2.6 and which I've
> > used in my local tree for 6 months now. It removes a useless NULL check
> > in zlib_inflateInit2_(), since 'z' is already dereferenced one line
> > before the test. Can in go in 2.4.30 please ?
>
> I don't see how such a cleanup-only patch would be a candidate for 2.4
> at all, let alone to go into a -rc3 or a 2.4.30 final at this stage...
>
> Can you explain why this one is so important that it has to go in so
> late?
On the contrary, it's just because it's not important at all that I
thought it could go in, the same way as other parts of unused code
got removed in rc2 (eg: jfs aops). As to the fact that it's late,
well, I would have prefered sending it sooner, but I simply don't
decide when I have spare time for this.
I have no problem at all with all these patches not merged, I simply
think that it makes maintainers' work easier to support homogeneous
code across versions with the least possible dead code, especially
when it comes to simple patches like this one. If you think it's better
to keep unused code because it makes debugging funnier, OK, that's fine.
Anyway, I'm just proposing, maintainers decide.
Willy
next prev parent reply other threads:[~2005-03-26 12:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 0:46 Linux 2.4.30-rc2 Marcelo Tosatti
2005-03-26 10:42 ` Willy Tarreau
2005-03-26 10:50 ` Willy Tarreau
2005-03-26 10:59 ` Willy Tarreau
2005-03-26 21:41 ` David S. Miller
2005-03-26 11:22 ` Willy Tarreau
2005-03-26 11:44 ` Arjan van de Ven
2005-03-26 12:27 ` Willy Tarreau [this message]
2005-03-26 16:07 ` Marcelo Tosatti
2005-03-26 11:34 ` Willy Tarreau
2005-03-26 11:46 ` Arjan van de Ven
2005-03-26 12:29 ` Willy Tarreau
2005-03-27 17:50 ` Andi Kleen
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=20050326122706.GA14756@alpha.home.local \
--to=willy@w.ods.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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