1. 01 2月, 2009 2 次提交
    • L
      Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6 · f984d024
      Linus Torvalds 提交于
      * git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6:
        igb: fix link reporting when using sgmii
        igb: prevent skb_over panic w/ mtu smaller than 1K
        igb: Fix DCA errors and do not use context index for 82576
        ipv6: compile fix for ip6mr.c
        packet: Avoid lock_sock in mmap handler
        sfc: Replace stats_enabled flag with a disable count
        sfc: SFX7101/SFT9001: Fix AN advertisements
        sfc: SFT9001: Always enable XNP exchange on SFT9001 rev B
        sfc: Update board info for hardware monitor on SFN4111T-R5 and later
        sfc: Test for PHYXS faults whenever we cannot test link state bits
        sfc: Reinitialise the PHY completely in case of a PHY or NIC reset
        sfc: Fix post-reset MAC selection
        sfc: SFN4111T: Fix GPIO sharing between I2C and FLASH_CFG_1
        sfc: SFT9001: Fix speed reporting in 1G PHY loopback
        sfc: SFX7101: Remove workaround for bad link training
        sfc: SFT9001: Enable robust link training
        sky2: fix hard hang with netconsoling and iface going up
      f984d024
    • L
      Stop playing silly games with the VM_ACCOUNT flag · fc8744ad
      Linus Torvalds 提交于
      The mmap_region() code would temporarily set the VM_ACCOUNT flag for
      anonymous shared mappings just to inform shmem_zero_setup() that it
      should enable accounting for the resulting shm object.  It would then
      clear the flag after calling ->mmap (for the /dev/zero case) or doing
      shmem_zero_setup() (for the MAP_ANON case).
      
      This just resulted in vma merge issues, but also made for just
      unnecessary confusion.  Use the already-existing VM_NORESERVE flag for
      this instead, and let shmem_{zero|file}_setup() just figure it out from
      that.
      
      This also happens to make it obvious that the new DRI2 GEM layer uses a
      non-reserving backing store for its object allocation - which is quite
      possibly not intentional.  But since I didn't want to change semantics
      in this patch, I left it alone, and just updated the caller to use the
      new flag semantics.
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      fc8744ad
  2. 31 1月, 2009 22 次提交
  3. 30 1月, 2009 16 次提交