The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Willy Tarreau <wtarreau@exosec.fr>
To: linux-kernel@vger.kernel.org
Subject: linux-2.4.29-hf7 (minor update)
Date: Tue, 5 Apr 2005 23:11:00 +0200	[thread overview]
Message-ID: <20050405211100.GA28029@exosec.fr> (raw)

Hi All,

just for completeness, I've updated the hotfix tree to hf7. The
changelog is ridiculously small (2 patches: 1 doc, 1 minor). The
2.4.29-hf tree is now up to date with 2.4.30. I will start the
2.4.30-hf soon (when 2.4.31-pre emerges), and will keep updating
2.4.29-hf as long as possible. For this, I'll have to make my
scripts a bit smarter to reduce the dual work, so first 2.4.30-hf
releases might be delayed a bit.

After one full 2.4 release, it seems that the 2.4-hf tree starts
to pay off : one patch which was finally removed in 2.4.30-rc4
never got its way to 2.4-hf and a potential problem affecting
usb-pwc for one 2.4.30 user theorically should not concern
2.4.29-hf. May be those will help maintainers and users of recent
kernels to find where their problem appeared ? Time will tell...

In the mean time, the patches are available at the usual store :

     http://linux.exosec.net/kernel/2.4-hf/


Regards,
Willy

--
Changelog From 2.4.29-hf6 to 2.4.29-hf7 (semi-automated)
---------------------------------------
'+' = added ; '-' = removed


+ bogus-mc_list-deletion-1                                         (Herbert Xu)

  Looks like I made a nasty typo in the 2.4 backport.  When entries
  are unlinked from mc_list, we link the list up with the regular
  hash bucket list by using next instead of bind_next!

+ recent-kernels-need-modutils-2414-1                           (Willy Tarreau)

  From Keith Owens:
  > You need modutils >= 2.4.14 to use the combination of
  > CONFIG_MODVERSIONS with EXPORT_SYMBOL_GPL() on 2.4 kernels.


END.



                 reply	other threads:[~2005-04-05 21:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050405211100.GA28029@exosec.fr \
    --to=wtarreau@exosec.fr \
    --cc=linux-kernel@vger.kernel.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