11 Aug, 2010

1 commit


22 May, 2010

3 commits

  • * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6: (69 commits)
    fix handling of offsets in cris eeprom.c, get rid of fake on-stack files
    get rid of home-grown mutex in cris eeprom.c
    switch ecryptfs_write() to struct inode *, kill on-stack fake files
    switch ecryptfs_get_locked_page() to struct inode *
    simplify access to ecryptfs inodes in ->readpage() and friends
    AFS: Don't put struct file on the stack
    Ban ecryptfs over ecryptfs
    logfs: replace inode uid,gid,mode initialization with helper function
    ufs: replace inode uid,gid,mode initialization with helper function
    udf: replace inode uid,gid,mode init with helper
    ubifs: replace inode uid,gid,mode initialization with helper function
    sysv: replace inode uid,gid,mode initialization with helper function
    reiserfs: replace inode uid,gid,mode initialization with helper function
    ramfs: replace inode uid,gid,mode initialization with helper function
    omfs: replace inode uid,gid,mode initialization with helper function
    bfs: replace inode uid,gid,mode initialization with helper function
    ocfs2: replace inode uid,gid,mode initialization with helper function
    nilfs2: replace inode uid,gid,mode initialization with helper function
    minix: replace inode uid,gid,mode init with helper
    ext4: replace inode uid,gid,mode init with helper
    ...

    Trivial conflict in fs/fs-writeback.c (mark bitfields unsigned)

    Linus Torvalds
     
  • ADDPART_FLAG_RAID was introduced in commit d18d768, and most places were
    converted to use it instead of a hardcoded value. However, some places seem
    to have been missed.

    Change all of them to the symbolic names via the following semantic patch:

    @@
    struct parsed_partitions *state;
    expression E;
    @@
    (
    - state->parts[E].flags = 1
    + state->parts[E].flags = ADDPART_FLAG_RAID
    |
    - state->parts[E].flags |= 1
    + state->parts[E].flags |= ADDPART_FLAG_RAID
    |
    - state->parts[E].flags = 2
    + state->parts[E].flags = ADDPART_FLAG_WHOLEDISK
    |
    - state->parts[E].flags |= 2
    + state->parts[E].flags |= ADDPART_FLAG_WHOLEDISK
    )

    Signed-off-by: Cesar Eduardo Barros
    Signed-off-by: Al Viro

    Cesar Eduardo Barros
     
  • Make the following changes to partition check code.

    * Add ->bdev to struct parsed_partitions.

    * Introduce read_part_sector() which is a simple wrapper around
    read_dev_sector() which takes struct parsed_partitions *state
    instead of @bdev.

    * For functions which used to take @state and @bdev, drop @bdev. For
    functions which used to take @bdev, replace it with @state.

    * While updating, drop superflous checks on NULL state/bdev in ldm.c.

    This cleans up the API a bit and enables better handling of IO errors
    during partition check as the generic partition check code now has
    much better visibility into what went wrong in the low level code
    paths.

    Signed-off-by: Tejun Heo
    Cc: Ben Hutchings
    Acked-by: David S. Miller
    Signed-off-by: Jens Axboe

    Tejun Heo
     

05 Dec, 2006

1 commit


01 Jul, 2006

1 commit


28 Mar, 2006

1 commit

  • This removes statically assigned platform numbers and reworks the
    powerpc platform probe code to use a better mechanism. With this,
    board support files can simply declare a new machine type with a
    macro, and implement a probe() function that uses the flattened
    device-tree to detect if they apply for a given machine.

    We now have a machine_is() macro that replaces the comparisons of
    _machine with the various PLATFORM_* constants. This commit also
    changes various drivers to use the new macro instead of looking at
    _machine.

    Signed-off-by: Benjamin Herrenschmidt
    Signed-off-by: Paul Mackerras

    Benjamin Herrenschmidt
     

17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds