From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: "Alexey Dobriyan" <adobriyan@gmail.com>,
"René Rebe" <rene@exactcode.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.23
Date: Wed, 10 Oct 2007 15:13:03 +0400 [thread overview]
Message-ID: <470CB3BF.2040904@msgid.tls.msk.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0710101250520.22916@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Oct 10 2007 14:36, Alexey Dobriyan wrote:
>>>>> --- linux-2.6.23/include/linux/mm.h.vanilla
>>>>> +++ linux-2.6.23/include/linux/mm.h
>>>>> +struct super_block;
>>>>> extern void drop_pagecache_sb(struct super_block *);
>>>>> void drop_pagecache(void);
>>>>> void drop_slab(void);
>>>>>
>>>>> You probably end up fixing it some other way, but as I do not know this
>>>>> file inside out I just wanted to drop a note.
>>>> You have some strange vanilla kernel. 2.6.23 doesn't have this prototype.
>>> The same happens here as well.
>>>
>>> -rw-rw-r-- 1 mjt mjt 45488158 Oct 9 20:48 linux-2.6.23.tar.bz2
>>> 2cc2fd4d521dc5d7cfce0d8a9d1b3472 linux-2.6.23.tar.bz2
>>>
>>> (timestamp is in UTC) Downloaded yesterday, 3 hours after an announce,
>>> from http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.23.tar.bz2 .
>> Strange. Same size, same md5, no super_block in mm.h, though
>
> Does someone still have the broken tarball?
>
> There has not been any drop_pagecache_sb anytime between 2.6.23-rc1
> and 2.6.23. drop_pagecache_sb reminds me of reiser4, too.
ghhrm. That's nonsense. I found where that struct super_block come
from -- it's from unionfs patches for 2.6.22, which I forgot to
update for 2.6.23 (I just dropped new kernel tarball into my
build directory together with other patches and ran usual build
procedure). It's a definitely false alarm - the tarball is
fine.
/mjt
next prev parent reply other threads:[~2007-10-10 11:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 20:54 Linux 2.6.23 Linus Torvalds
2007-10-10 6:12 ` Nicholas Miell
2007-10-10 10:14 ` Ingo Molnar
2007-10-11 1:20 ` Nicholas Miell
2007-10-11 2:34 ` Zhang, Yanmin
2007-10-11 13:32 ` Ingo Molnar
2007-10-11 9:16 ` Nick Piggin
2007-10-12 5:46 ` Ingo Molnar
2007-10-11 14:15 ` Nick Piggin
2007-10-12 12:21 ` Bill Davidsen
2007-10-10 7:44 ` René Rebe
2007-10-10 8:37 ` Alexey Dobriyan
2007-10-10 9:12 ` Michael Tokarev
2007-10-10 10:36 ` Alexey Dobriyan
2007-10-10 10:53 ` Jan Engelhardt
2007-10-10 11:13 ` Michael Tokarev [this message]
2007-10-10 19:14 ` Ingo Molnar
2007-10-10 19:26 ` Michael Tokarev
2007-10-10 20:04 ` Andi Kleen
2007-10-10 23:27 ` Krzysztof Halasa
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=470CB3BF.2040904@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=adobriyan@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rene@exactcode.de \
--cc=torvalds@linux-foundation.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