16 Jan, 2009

40 commits

  • We just fix up the reference parameters as the others are dealt with by
    arithmetic promotion rules and don't cause warnings.

    This removes warnings like this:

    arch/powerpc/platforms/ps3/interrupt.c:327: warning: passing argument 1 of 'lv1_construct_event_receive_port' from incompatible pointer type

    Also, these:

    drivers/ps3/ps3-vuart.c:462: warning: passing argument 4 of 'ps3_vuart_raw_read' from incompatible pointer type
    drivers/ps3/ps3-vuart.c:592: warning: passing argument 4 of 'ps3_vuart_raw_read' from incompatible pointer type

    Signed-off-by: Stephen Rothwell
    Acked-by: Geoff Levand
    Signed-off-by: Benjamin Herrenschmidt

    Stephen Rothwell
     
  • Push the dma_addr_t type usage all the way down to where the actual
    values are manipulated.

    Now that u64 is "unsigned long long", this removes warnings like:

    arch/powerpc/platforms/ps3/system-bus.c:532: warning: passing argument 4 of 'ps3_dma_map' from incompatible pointer type
    arch/powerpc/platforms/ps3/system-bus.c:649: warning: passing argument 4 of 'ps3_dma_map' from incompatible pointer type

    Signed-off-by: Stephen Rothwell
    Acked-by: Geoff Levand
    Signed-off-by: Benjamin Herrenschmidt

    Stephen Rothwell
     
  • Also silences this warning:

    arch/powerpc/platforms/ps3/setup.c:275: warning: initialization from incompatible pointer type

    Signed-off-by: Stephen Rothwell
    Acked-by: Geoff Levand
    Signed-off-by: Benjamin Herrenschmidt

    Stephen Rothwell
     
  • This is a powerpc specific driver.

    Signed-off-by: Stephen Rothwell
    Signed-off-by: Benjamin Herrenschmidt

    Stephen Rothwell
     
  • …l/git/tip/linux-2.6-tip

    * 'sched-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
    sched: sched_slice() fixlet
    sched: fix update_min_vruntime
    sched: SCHED_OTHER vs SCHED_IDLE isolation
    sched: SCHED_IDLE weight change
    sched: fix bandwidth validation for UID grouping
    Revert "sched: improve preempt debugging"

    Linus Torvalds
     
  • * git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6:
    sparc64: Fix UP build failure.

    Linus Torvalds
     
  • * git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6: (95 commits)
    b44: GFP_DMA skb should not escape from driver
    korina: do not use IRQF_SHARED with IRQF_DISABLED
    korina: do not stop queue here
    korina: fix handling tx_chain_tail
    korina: do tx at the right position
    korina: do schedule napi after testing for it
    korina: rework korina_rx() for use with napi
    korina: disable napi on close and restart
    korina: reset resource buffer size to 1536
    korina: fix usage of driver_data
    bnx2x: First slow path interrupt race
    bnx2x: MTU Filter
    bnx2x: Indirection table initialization index
    bnx2x: Missing brackets
    bnx2x: Fixing the doorbell size
    bnx2x: Endianness issues
    bnx2x: VLAN tagged packets without VLAN offload
    bnx2x: Protecting the link change indication
    bnx2x: Flow control updated before reporting the link
    bnx2x: Missing mask when calculating flow control
    ...

    Linus Torvalds
     
  • * 'hwmon-for-linus' of git://jdelvare.pck.nerim.net/jdelvare-2.6:
    hwmon: (abituguru3) Fix CONFIG_DMI=n fallback to probe
    hwmon: (abituguru3) Enable DMI probing feature on IN9 32X MAX
    hwmon: (abituguru3) Match partial DMI board name strings
    hwmon: Add a driver for the ADT7475 hardware monitoring chip
    hwmon: (k8temp) Fix temperature reporting for (most) K8 RevG CPUs
    hwmon: (k8temp) Fix wrong sensor selection for AMD K8 RevF/RevG CPUs
    hwmon: (k8temp) Warn about fam F rev F errata

    Linus Torvalds
     
  • If INET=y and INFINIBAND=y, but IPV6=m then INFINIBAND_ADDR_TRANS is set
    to n and the RDMA CM functions rdma_connect() et al are not built.
    However, the current config dependencies allow NET_9P_RDMA to be selected
    in this, which leads to a build failure. Fix this by adding a dependency
    on INFINIBAND_ADDR_TRANS to disallow NET_9P_RDMA in this case.

    Reported-by: Randy Dunlap
    Signed-off-by: Roland Dreier
    Acked-by: Randy Dunlap
    Tested-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Roland Dreier
     
  • We used to just write changed page for IS_DIRSYNC inodes. But we also
    have to update the directory inode itself just for the case that we've
    allocated a new block and changed i_size.

    [akpm@linux-foundation.org: still sync the data page]
    Signed-off-by: Jan Kara
    Tested-by: Pavel Machek
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jan Kara
     
  • Carry out the PM-routine interface change in the USB OTG pathway. This
    was omitted from the earlier interface-change patch by mistake.

    Signed-off-by: Alan Stern
    Cc: Greg KH
    Cc: Russell King
    Cc: Felipe Balbi
    Cc: Tony Lindgren
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Brownell
     
  • Impact: fix 15 make headers_check warnings:

    include of is preferred over

    Signed-off-by: Jaswinder Singh Rajput
    Cc: Ingo Molnar
    Cc: Sam Ravnborg
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jaswinder Singh Rajput
     
  • (suppose: memcg->use_hierarchy == 0 and memcg->swappiness == 60)

    echo 10 > /memcg/0/swappiness |
    mem_cgroup_swappiness_write() |
    ... | echo 1 > /memcg/0/use_hierarchy
    | mkdir /mnt/0/1
    | sub_memcg->swappiness = 60;
    memcg->swappiness = 10; |

    In the above scenario, we end up having 2 different swappiness
    values in a single hierarchy.

    We should hold cgroup_lock() when cheking cgrp->children list.

    Signed-off-by: Li Zefan
    Acked-by: KAMEZAWA Hiroyuki
    Cc: Balbir Singh
    Cc: Paul Menage
    Cc: Daisuke Nishimura
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Li Zefan
     
  • At system boot when creating the top cgroup, mem_cgroup_create() calls
    enable_swap_cgroup() which is marked as __init, so mark
    mem_cgroup_create() as __ref to avoid false section mismatch warning.

    Reported-by: Rakib Mullick
    Signed-off-by: Li Zefan
    Acked-by; KAMEZAWA Hiroyuki
    Cc: Balbir Singh
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Li Zefan
     
  • The LED on HP notebooks is connected through ACPI. That unfortunately
    means that it needs to be delayed by using schedule_work() to avoid
    calling the ACPI interpreter from an invalid context.

    [akpm@linux-foundation.org: use flush_work() rather than sort-of reimplementing it]
    Signed-off-by: Pavel Machek
    Cc: Éric Piel
    Cc: Len Brown
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Machek
     
  • Fix lis3 documentation to fit into 80 columns.

    Signed-off-by: Pavel Machek
    Cc: Éric Piel
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Machek
     
  • Move the second part of the HP laptop disk protection functionality (a red
    led) to the same driver. From a purely Linux developer's point of view,
    the led and the accelerometer have nothing related. However, they
    correspond to the same ACPI functionality, and so will always be used
    together, moreover as they share the same ACPI PNP alias, there is no
    other simple to allow to have same loaded at the same time if they are not
    in the same module. Also make it requires the led class to compile and
    update the Kconfig text.

    Signed-off-by: Pavel Machek
    Signed-off-by: Eric Piel
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Eric Piel
     
  • David points out that the idr_remove_all() function returns unused slabs
    to the kmem cache, but needs to zero them first or else they will be
    uninitialized upon next use. This causes crashes which have been observed
    in the firewire subsystem.

    He fixed this by zeroing the object before freeing it in idr_remove_all().

    But we agree that simply removing the constructor and zeroing the object
    at allocation time is simpler than relying upon slab constructor machinery
    and might even be faster.

    This problem was introduced by "idr: make idr_remove rcu-safe" (commit
    cf481c20c476ad2c0febdace9ce23f5a4db19582), which was first released in
    2.6.27.

    There are no known codesites which trigger this bug in 2.6.27 or 2.6.28.
    The post-2.6.28 firewire changes are the only known triggerer.

    There might of course be not-yet-discovered triggerers in 2.6.27 and
    2.6.28, and there might be out-of-tree triggerers which are added to those
    kernel versions. I'll let the -stable guys decide whether they want to
    backport this fix.

    Reported-by: David Moore
    Cc: Stefan Richter
    Cc: Nadia Derbey
    Cc: Paul E. McKenney
    Cc: Manfred Spraul
    Cc: Kristian Hgsberg
    Acked-by: Pekka Enberg
    Cc:
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andrew Morton
     
  • As it's just a single call to __get_free_page().

    Signed-off-by: Ivan Kokshaysky
    Cc: Richard Henderson
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ivan Kokshaysky
     
  • Signed-off-by: Ivan Kokshaysky
    Cc: Richard Henderson
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ivan Kokshaysky
     
  • Unlike other alphas, marvel doesn't have real PC-style CMOS clock hardware
    - RTC accesses are emulated via PAL calls. Unfortunately, for unknown
    reason these calls work only on CPU #0. So current implementation for
    arbitrary CPU makes CMOS_READ/WRITE to be executed on CPU #0 via IPI.
    However, for obvious reason this doesn't work with standard
    get/set_rtc_time() functions, where a bunch of CMOS accesses is done with
    disabled interrupts.

    Solved by making the IPI calls for entire get/set_rtc_time() functions,
    not for individual CMOS accesses. Which is also a lot more effective
    performance-wise.

    The patch is largely based on the code from Jay Estabrook.
    My changes:
    - tweak asm-generic/rtc.h by adding a couple of #defines to
    avoid a massive code duplication in arch/alpha/include/asm/rtc.h;
    - sys_marvel.c: fix get/set_rtc_time() return values (Jay's FIXMEs).

    NOTE: this fixes *only* LIB_RTC drivers. Legacy (CONFIG_RTC) driver
    wont't work on marvel. Actually I think that we should just disable
    CONFIG_RTC on alpha (maybe in 2.6.30?), like most other arches - AFAIK,
    all modern distributions use LIB_RTC anyway.

    Signed-off-by: Ivan Kokshaysky
    Cc: Richard Henderson
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ivan Kokshaysky
     
  • Recently introduced generic pci_common_swizzle() relies on bus->self
    being NULL for the root PCI bus. But on nautilus bus->self points to
    the host bridge device, which is necessary as we do a root bus sizing
    on this system. As a result, pci_common_swizzle() loops infinitely.
    This worked until 2.6.29-rc1 because the alpha-specific swizzle routine
    checked for bus->parent == NULL (instead of bus->self).

    Fixed by clearing bus->self after bus sizing is done.

    Signed-off-by: Ivan Kokshaysky
    Cc: Richard Henderson
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ivan Kokshaysky
     
  • init_srm_irq() deals with irq's #16 and above, but size of irq_desc
    array on nautilus and some other system types is 16. So gcc-4.3
    complains that "array subscript is above array bounds", even though
    this function is never called on those systems.

    This adds a check for NR_IRQS for detailed analysis
    of the problem.

    Signed-off-by: Ivan Kokshaysky
    Cc: Richard Henderson
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ivan Kokshaysky
     
  • Revert commit e97a630eb0f5b8b380fd67504de6cedebb489003 ("mm: vmalloc use
    mutex for purge")

    Bryan Donlan reports:

    : After testing 2.6.29-rc1 on xen-x86 with a btrfs root filesystem, I
    : got the OOPS quoted below and a hard freeze shortly after boot.
    : Boot messages and config are attached.
    :
    : ------------[ cut here ]------------
    : Kernel BUG at c05ef80d [verbose debug info unavailable]
    : invalid opcode: 0000 [#1] SMP
    : last sysfs file: /sys/block/xvdc/size
    : Modules linked in:
    :
    : Pid: 0, comm: swapper Not tainted (2.6.29-rc1 #6)
    : EIP: 0061:[] EFLAGS: 00010087 CPU: 2
    : EIP is at schedule+0x7cd/0x950
    : EAX: d5aeca80 EBX: 00000002 ECX: 00000000 EDX: d4cb9a40
    : ESI: c12f5600 EDI: d4cb9a40 EBP: d6033fa4 ESP: d6033ef4
    : DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0069
    : Process swapper (pid: 0, ti=d6032000 task=d6020b70 task.ti=d6032000)
    : Stack:
    : 000d85bc 00000000 000186a0 00000000 0dd11410 c0105417 c12efe00 0dc367c3
    : 00000011 c0105d46 d5a5d310 deadbeef d4cb9a40 c07cc600 c05f1340 c12e0060
    : deadbeef d6020b70 d6020d08 00000002 c014377d 00000000 c12f5600 00002c22
    : Call Trace:
    : [] xen_force_evtchn_callback+0x17/0x30
    : [] check_events+0x8/0x12
    : [] _spin_unlock_irqrestore+0x20/0x40
    : [] hrtimer_start_range_ns+0x12d/0x2e0
    : [] tick_nohz_restart_sched_tick+0x146/0x160
    : [] cpu_idle+0xa5/0xc0

    and bisected it to this commit.

    Let's remove it now while we have a think about the problem.

    Reported-by: Bryan Donlan
    Tested-by: Christophe Saout
    Cc: Nick Piggin
    Cc: Ingo Molnar
    Cc: Jeremy Fitzhardinge
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andrew Morton
     
  • In previous implementation, mem_cgroup_try_charge checked the return
    value of mem_cgroup_try_to_free_pages, and just retried if some pages
    had been reclaimed.
    But now, try_charge(and mem_cgroup_hierarchical_reclaim called from it)
    only checks whether the usage is less than the limit.

    This patch tries to change the behavior as before to cause oom less
    frequently.

    Signed-off-by: Daisuke Nishimura
    Acked-by: Balbir Singh
    Acked-by: KAMEZAWA Hiroyuki
    Cc: Pavel Emelyanov
    Cc: Li Zefan
    Cc: Paul Menage
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Daisuke Nishimura
     
  • If root_mem has no children, last_scaned_child is set to root_mem itself.
    But after some children added to root_mem, mem_cgroup_get_next_node can
    mem_cgroup_put the root_mem although root_mem has not been mem_cgroup_get.

    This patch fixes this behavior by:

    - Set last_scanned_child to NULL if root_mem has no children or DFS
    search has returned to root_mem itself(root_mem is not a "child" of
    root_mem). Make mem_cgroup_get_first_node return root_mem in this case.
    There are no mem_cgroup_get/put for root_mem.

    - Rename mem_cgroup_get_next_node to __mem_cgroup_get_next_node, and
    mem_cgroup_get_first_node to mem_cgroup_get_next_node. Make
    mem_cgroup_hierarchical_reclaim call only new mem_cgroup_get_next_node.

    Signed-off-by: Daisuke Nishimura
    Cc: Balbir Singh
    Cc: KAMEZAWA Hiroyuki
    Cc: Pavel Emelyanov
    Cc: Li Zefan
    Cc: Paul Menage
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Daisuke Nishimura
     
  • There is a bug in error path of mem_cgroup_move_parent.

    Extra refcnt got from try_charge should be dropped, and usages incremented
    by try_charge should be decremented in both error paths:

    A: failure at get_page_unless_zero
    B: failure at isolate_lru_page

    This bug makes this parent directory unremovable.

    In case of A, rmdir doesn't return, because res.usage doesn't go down to 0
    at mem_cgroup_force_empty even after all the pc in lru are removed.

    In case of B, rmdir fails and returns -EBUSY, because it has extra ref
    counts even after res.usage goes down to 0.

    Signed-off-by: Daisuke Nishimura
    Acked-by: KAMEZAWA Hiroyuki
    Acked-by: Balbir Singh
    Cc: Pavel Emelyanov
    Cc: Li Zefan
    Cc: Paul Menage
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Daisuke Nishimura
     
  • In case of swapin, a new page is added to lru before it is charged,
    so page->pc->mem_cgroup points to NULL or last mem_cgroup the page
    was charged before.

    In the latter case, if the mem_cgroup has already freed by rmdir,
    the area pointed to by page->pc->mem_cgroup may have invalid data.

    Actually, I saw general protection fault.

    general protection fault: 0000 [#1] SMP
    last sysfs file: /sys/devices/system/cpu/cpu15/cache/index1/shared_cpu_map
    CPU 4
    Modules linked in: ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp ipv6 autofs4 hidp rfcomm l2cap bluetooth sunrpc dm_mirror dm_region_hash dm_log dm_multipath dm_mod rfkill input_polldev sbs sbshc battery ac lp sg ide_cd_mod cdrom button serio_raw acpi_memhotplug parport_pc e1000 rtc_cmos parport rtc_core rtc_lib i2c_i801 i2c_core shpchp pcspkr ata_piix libata megaraid_mbox megaraid_mm sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd [last unloaded: microcode]
    Pid: 26038, comm: page01 Tainted: G W 2.6.28-rc9-mm1-mmotm-2008-12-22-16-14-f2ab3dea #1
    RIP: 0010:[] [] update_page_reclaim_stat+0x2f/0x42
    RSP: 0000:ffff8801ee457da8 EFLAGS: 00010002
    RAX: 32353438312021c8 RBX: 0000000000000000 RCX: 32353438312021c8
    RDX: 0000000000000000 RSI: ffff8800cb0b1000 RDI: ffff8801164d1d28
    RBP: ffff880110002cb8 R08: ffff88010f2eae23 R09: 0000000000000001
    R10: ffff8800bc514b00 R11: ffff880110002c00 R12: 0000000000000000
    R13: ffff88000f484100 R14: 0000000000000003 R15: 00000000001200d2
    FS: 00007f8a261726f0(0000) GS:ffff88010f2eaa80(0000) knlGS:0000000000000000
    CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    CR2: 00007f8a25d22000 CR3: 00000001ef18c000 CR4: 00000000000006e0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Process page01 (pid: 26038, threadinfo ffff8801ee456000, task ffff8800b585b960)
    Stack:
    ffffe200071ee568 ffff880110001f00 0000000000000000 ffffffff8028ea17
    ffff88000f484100 0000000000000000 0000000000000020 00007f8a25d22000
    ffff8800bc514b00 ffffffff8028ec34 0000000000000000 0000000000016fd8
    Call Trace:
    [] ? ____pagevec_lru_add+0xc1/0x13c
    [] ? drain_cpu_pagevecs+0x36/0x89
    [] ? swapin_readahead+0x78/0x98
    [] ? handle_mm_fault+0x3d9/0x741
    [] ? do_page_fault+0x3ce/0x78c
    [] ? trace_hardirqs_off_thunk+0x3a/0x3c
    [] ? page_fault+0x1f/0x30
    Code: cc 55 48 8d af b8 0d 00 00 48 89 f7 53 89 d3 e8 39 85 02 00 48 63 d3 48 ff 44 d5 10 45 85 e4 74 05 48 ff 44 d5 00 48 85 c0 74 0e ff 44 d0 10 45 85 e4 74 04 48 ff 04 d0 5b 5d 41 5c c3 41 54
    RIP [] update_page_reclaim_stat+0x2f/0x42
    RSP

    Signed-off-by: Daisuke Nishimura
    Acked-by: KAMEZAWA Hiroyuki
    Cc: Balbir Singh
    Cc: Pavel Emelyanov
    Cc: Li Zefan
    Cc: Paul Menage
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Daisuke Nishimura
     
  • The light sensors ALV0 and ALV1 on newer MacBooks (early 2008 and later)
    changed to report 10 bytes instead the earlier 6, and the sensor encoding
    subsequently changed. As a result, the reported light sensors readings
    are much too low.

    Via experiments leading up to this patch, it seems only the ALV0 is
    reporting data, and the most useful value therein is a 10-bit big-endian
    value at offset 6. This suggests that a new protocol was added as a
    backward-compatible replacement on top of the old one.

    This patch makes applesmc report the improved light sensor reading for the
    new machines, on a scale in conformance with earlier ones.

    Signed-off-by: Alex Murray
    Signed-off-by: Henrik Rydberg
    Cc: Nicolas Boichat
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Alex Murray
     
  • Signed-off-by: Andy Whitcroft
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     
  • In the general use case struct seq_operations should be a const object.
    Check for and warn where it is not.

    Cc: Ingo Molnar
    Signed-off-by: Andy Whitcroft
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     
  • We should not be continuing a braced section with an if, for example:

    if (...) {
    } if (...) {
    }

    Detect this and suggest adding a newline.

    Signed-off-by: Andy Whitcroft
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     
  • When we allow return to have surrounding parentheses when containing
    comparison operators we are not correctly handling the case where the
    values contain array sufffixes. Squash them.

    Signed-off-by: Andy Whitcroft
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     
  • We should not be complaining about the prefix spacing for types and casts.
    We are triggering here because the check for spacing between '*'s is
    overly loose. Tighten this up.

    Signed-off-by: Andy Whitcroft
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     
  • If the #if opening statement is not in the context then the context stack
    can be empty. Handle this by ensuring there is always a blank entry in
    the stack.

    Signed-off-by: Andy Whitcroft
    Tested-by: Dhaval Giani
    Cc: Ingo Molnar
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     
  • Two nbd-clients at same time are bad idea, and cause WARN_ON from nbd in
    2.6.28-rc7 from sysfs_add_one. This simply prevents that from happening.

    To reproduce:

    cat /dev/zero | head -c 10000000 > /tmp/delme.fstest.fs
    nbd-server 9100 -l /anyone.can.connect > /tmp/delme.fstest.fs &
    sleep 1
    nbd-client localhost 9100 /dev/nd0 &
    nbd-client localhost 9100 /dev/nd0 &

    Signed-off-by: Pavel Machek
    Acked-by: Paul Clements
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Machek
     
  • Use the standard magic.h for btrfs and squashfs.

    Signed-off-by: Qinghuang Feng
    Cc: Phillip Lougher
    Cc: Chris Mason
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Qinghuang Feng
     
  • Now that people are using freezer for non-suspend/hibernation stuff, it
    should have separate maintainers entry so that it is easier to find.

    Signed-off-by: Pavel Machek
    Acked-by: Rafael J. Wysocki
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Machek
     
  • Fix __request_region() parameter kernel-doc notation and parameter name:

    Warning(linux-2.6.28-git10//kernel/resource.c:627): No description found for parameter 'flags'

    Signed-off-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     
  • Fix jbd header file kernel-doc notation:

    Warning(linux-2.6.28-git13//include/linux/jbd.h:823): No description found for parameter 'j_average_commit_time'

    Signed-off-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy Dunlap