mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Richard Purdie <richard@openedhand.com>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH RFC/testing] Upgrade the zlib_inflate library code to a recent version
Date: Tue, 4 Apr 2006 18:16:27 +0200	[thread overview]
Message-ID: <20060404161627.GH25130@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1144166212.6441.57.camel@localhost.localdomain>

On Tue, 4 April 2006 16:56:51 +0100, Richard Purdie wrote:
> On Tue, 2006-04-04 at 17:33 +0200, Jörn Engel wrote:
> > On Tue, 4 April 2006 16:18:08 +0100, Richard Purdie wrote: 
> > > Upgrade the zlib_inflate implementation in the kernel from a patched
> > > version 1.1.3 to a patched 1.2.3. 
> > 
> > s/1.1.3/1.1.4/
> >
> > I once pulled all the bugfixes between the versions into the kernel.
> 
> That's not what the header says :)

Well, the complete patch from 1.1.3 to 1.1.4 was rather big.  Every
single copyright line got updated to a current date, without any other
changes in those files.  I found it rather silly and took the bugfixes
only. ;)

> > > +#if 0
> > > +int zlib_inflatePrime(z_streamp strm, int bits, int value)
> > 
> > Was this code dead in 1.2.3 as well?
> 
> This code was commented out in the kernel by Adrian Bunk as it has no
> users and I just followed that example when updating  I'm sure if
> someone needed it, it could be enabled.

My thinking was rather that we could remove it.  #if 0 has an
advantage in case you made a mistake - easy to revert.  But after a
while...

> > > +#ifndef PKZIP_BUG_WORKAROUND
> > 
> > For the kernel, we can remove compat code against DOS compilers, etc.
> > In this particular case, I believe we can just consider data
> > compressed with PKZIP to be illegal and throw an error.
> 
> Agreed, there are places it can be tidied up a bit further. I was trying
> not to make too many changes so any future updates against zlib are
> easier.

Fair enough.

Jörn

-- 
Data expands to fill the space available for storage.
-- Parkinson's Law

  reply	other threads:[~2006-04-04 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 15:18 Richard Purdie
2006-04-04 15:33 ` Jörn Engel
2006-04-04 15:56   ` Richard Purdie
2006-04-04 16:16     ` Jörn Engel [this message]
2006-04-04 15:38 ` Jan Engelhardt
2006-04-04 15:46   ` Jörn Engel
2006-04-05  8:37 ` Jörn Engel

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=20060404161627.GH25130@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@openedhand.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

all inboxes | Powered by JetHome®