On Thursday 08 February 2007, Arjan van de Ven wrote: > On Thu, 2007-02-08 at 02:46 -0500, Mike Frysinger wrote: > > was ufs_fs.h purposefully not exported to userspace or did it just slip > > through the cracks ? assuming the latter scenario, the attached patch > > touches up the relationship between ufs_fs.h and its sub headers (like > > ufs_fs_sb.h) so that we can export it ... the silo bootloader takes > > advantage of this header for example > > are you sure it actually uses anything from this header, and not just > assumes the magic number to be there?? > (also.. I kind of would think it reasonable for things with their own > UFS fs reader to have their own header) silo utilizes the structures and the random defines so that it can query UFS filesystems directly -mike
Attachment:
pgpvFaCOqetNJ.pgp
Description: PGP signature
- Follow-Ups:
- Re: [patch] export ufs_fs.h to userspace
- From: Arjan van de Ven <[email protected]>
- Re: [patch] export ufs_fs.h to userspace
- References:
- [patch] export ufs_fs.h to userspace
- From: Mike Frysinger <[email protected]>
- Re: [patch] export ufs_fs.h to userspace
- From: Arjan van de Ven <[email protected]>
- [patch] export ufs_fs.h to userspace
- Prev by Date: Re: EV_MSC / driver/input/input.c (Input Handler)
- Next by Date: INFO: possible circular locking dependency detected
- Previous by thread: Re: [patch] export ufs_fs.h to userspace
- Next by thread: Re: [patch] export ufs_fs.h to userspace
- Index(es):