From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] patch HTB to 2.4.19 problem
Date: Wed, 28 Aug 2002 17:48:54 +0000 [thread overview]
Message-ID: <marc-lartc-103055698704090@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103054101916025@msgid-missing>
On Wednesday 28 August 2002 15:21, Robert Penz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi!
>
> I keep getting following
>
> whitestar:/usr/src/linux-2.4.19# patch -p1 < ../htb3.6_2.4.17.diff
> patching file net/sched/Config.in
> patching file net/sched/Makefile
> patching file net/sched/sch_htb.c
> patching file include/linux/pkt_sched.h
> patching file net/sched/sch_api.c
> Hunk #1 FAILED at 1117.
> 1 out of 2 hunks FAILED -- saving rejects to file net/sched/sch_api.c.rej
> patching file lib/Makefile
> Reversed (or previously applied) patch detected! Assume -R? [n]
> Apply anyway? [n] y
> Hunk #1 FAILED at 8.
> 1 out of 1 hunk FAILED -- saving rejects to file lib/Makefile.rej
> patching file lib/rbtree.c
> Reversed (or previously applied) patch detected! Assume -R? [n]
You can safely ignore these errors. Just press enter on all questions.
If you check out the *.rej files, you will see that some of the htb patches
are already applied to the default linux kernel.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-08-28 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 13:21 [LARTC] patch HTB to 2.4.19 problem Robert Penz
2002-08-28 17:48 ` Stef Coene [this message]
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=marc-lartc-103055698704090@msgid-missing \
--to=stef.coene@docum.org \
--cc=lartc@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 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.