From: Mikael Pettersson <mikpe@csd.uu.se>
To: kai@tp1.ruhr-uni-bochum.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.22 broke modversions
Date: Mon, 17 Jun 2002 21:25:51 +0200 (MET DST) [thread overview]
Message-ID: <200206171925.VAA08686@harpo.it.uu.se> (raw)
On Mon, 17 Jun 2002 09:30:13 -0500 (CDT), Kai Germaschewski wrote:
>> Something in the 2.5.22 Makefile/Rule.make changes broke
>> modversions on my P4 box. ...
>
>You're right, thanks for the report. The fix is appended ;)
Thanks. The fix worked fine for me.
>(Whenever a .ver file is updated, include/linux/modversions.h is touched,
> so that during the build make only needs to check the timestamp
> of modversions.h instead of all the individual .ver files - do you see a
> problem with that?)
Nope, that should be ok.
/Mikael
next reply other threads:[~2002-06-17 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 19:25 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-17 14:59 2.5.22 broke modversions Holzrichter, Bruce
2002-06-17 12:32 Mikael Pettersson
2002-06-17 14:30 ` Kai Germaschewski
2002-06-17 14:45 ` Martin Dalecki
2002-06-17 15:30 ` Kai Germaschewski
2002-06-17 15:39 ` Martin Dalecki
2002-06-17 15:52 ` Kai Germaschewski
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=200206171925.VAA08686@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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 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.