public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: torvalds@transmeta.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"David S. Miller" <davem@redhat.com>,
	kaos@ocs.com.au, linux-kernel@vger.kernel.org, paulus@samba.org,
	davidm@hpl.hp.com, ralf@gnu.org, garzik@havoc.gtf.org
Subject: Re: [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does
Date: Fri, 01 Feb 2002 16:08:49 +0000	[thread overview]
Message-ID: <17075.1012579729@redhat.com> (raw)
In-Reply-To: <20020201151221.GA8404@vana.vc.cvut.cz>
In-Reply-To: <20020201151221.GA8404@vana.vc.cvut.cz>  <20020131.222643.85689058.davem@redhat.com> <E16WfDe-0005Jd-00@the-village.bc.nu> <20020201095510.D17412@havoc.gtf.org>


vandrove@vc.cvut.cz said:
>   I decided to use fs_initcall level, as nobody is using this yet. If
> jffs2 will get initialized by fs_initcall, we'll have to switch
> init_crc32 from fs_initcall to arch_initcall or even sooner - crc32
> initialization needs only working kmalloc, nothing else (and it could
> use static buffer happilly, as zeroes compress very good), so
> subsys_initcall could work too. 

JFFS2 won't actually use the crc32 routines till it tries to mount a file 
system, so you shouldn't have a problem unless you try to mount the rootfs 
before init_crc32().


--
dwmw2



  parent reply	other threads:[~2002-02-01 16:10 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020131.162549.74750188.davem@redhat.com>
2002-02-01  0:42 ` [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does Alan Cox
2002-02-01  0:30   ` David S. Miller
2002-02-01  3:46     ` Jeff Garzik
2002-02-01  4:25       ` David S. Miller
2002-02-01  4:48         ` Jeff Garzik
2002-02-01  5:59           ` David S. Miller
2002-02-01  5:10         ` Keith Owens
2002-02-01  5:12           ` Jeff Garzik
2002-02-01  5:18             ` Keith Owens
2002-02-01 13:42               ` Horst von Brand
2002-02-03 23:34                 ` Keith Owens
2002-02-04 20:14                   ` Horst von Brand
2002-02-01  6:01           ` David S. Miller
2002-02-01  6:11             ` Keith Owens
2002-02-01  6:26               ` David S. Miller
2002-02-01  6:43                 ` Keith Owens
2002-02-01 15:03                 ` Alan Cox
2002-02-01 14:55                   ` Jeff Garzik
2002-02-01 15:12                     ` Petr Vandrovec
2002-02-01 15:29                       ` VESA Anybody out there Martin Dalecki
2002-02-01 15:42                         ` Davidovac Zoran
2002-02-01 16:21                           ` Martin Dalecki
2002-02-01 16:33                             ` Thomas Capricelli
2002-02-01 16:53                               ` Martin Dalecki
2002-02-01 16:35                             ` Sergey S. Kostyliov
2002-02-01 16:37                           ` Anton Altaparmakov
2002-02-01 16:33                         ` Petr Baudis
2002-02-01 17:45                         ` The Candyman
2002-02-02 13:41                           ` Andreas Happe
2002-02-02 21:09                             ` Martin Dalecki
2002-02-05 17:05                         ` Pavel Machek
2002-02-01 16:08                     ` David Woodhouse [this message]
2002-02-04 13:24                     ` [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does Horst von Brand
2002-02-05  7:51                       ` Jeff Garzik
2002-02-01  4:18     ` H. Peter Anvin
2002-02-01  4:35       ` Jeff Garzik
2002-02-01 15:19     ` Alan Cox
2002-02-01 19:37     ` Rob Landley
2002-02-01 19:50       ` Jeff Garzik
2002-01-31 22:59 [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does not David S. Miller
2002-01-31 23:24 ` [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does Alan Cox
2002-01-31 23:21   ` Arnaldo Carvalho de Melo
2002-02-02 16:32     ` Denis Vlasenko
2002-02-02 12:57       ` Jens Axboe
2002-02-02 13:16         ` arjan
2002-02-02 13:52           ` Jens Axboe
2002-02-03 11:37       ` David Woodhouse
2002-01-31 23:43   ` Jeff Garzik
2002-01-31 23:45   ` David S. Miller
2002-02-01  0:32     ` Alan Cox
2002-02-01 10:07     ` Horst von Brand
2002-02-01 10:28       ` Keith Owens
2002-02-01 11:03         ` David S. Miller
2002-02-01 11:25           ` Keith Owens
2002-02-01 14:56             ` Jeff Garzik
2002-02-01  8:14   ` David Woodhouse
2002-02-02  2:12   ` Chris Wedgwood
2002-02-02  3:01     ` Andrew Morton
2002-02-02  7:30       ` Chris Wedgwood
2002-02-02  7:42         ` Daniel Jacobowitz
2002-02-02  8:08           ` Jeff Garzik
2002-02-02 19:20             ` Daniel Jacobowitz
2002-02-02  8:06         ` Jeff Garzik
2002-02-02  8:08         ` Keith Owens
2002-02-02  8:40           ` David Woodhouse
2002-02-02  8:59             ` Keith Owens
2002-02-02  9:14               ` David Woodhouse
2002-02-03  4:14   ` Eric W. Biederman
2002-02-03  7:01     ` Ralf Baechle
2002-02-03  9:13       ` Chris Wedgwood
2002-02-03 12:16       ` David Woodhouse
2002-02-03 12:33         ` Chris Wedgwood
2002-02-03 12:47         ` David Woodhouse
2002-02-03 13:40       ` Alan Cox

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=17075.1012579729@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=garzik@havoc.gtf.org \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=ralf@gnu.org \
    --cc=torvalds@transmeta.com \
    --cc=vandrove@vc.cvut.cz \
    /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