09 Feb, 2013

1 commit

  • OVMF (an implementation of UEFI based on TianoCore used in virtual
    environments) now has the ability to boot Linux natively; this is used
    for "qemu -kernel" and similar things in a UEFI environment.

    Accordingly, assign it a bootloader ID.

    Signed-off-by: H. Peter Anvin
    Cc: David Woodhouse

    H. Peter Anvin
     

05 Feb, 2013

2 commits


01 Feb, 2013

2 commits


31 Jan, 2013

1 commit

  • Pull x86 EFI fixes from Peter Anvin:
    "This is a collection of fixes for the EFI support. The controversial
    bit here is a set of patches which bumps the boot protocol version as
    part of fixing some serious problems with the EFI handover protocol,
    used when booting under EFI using a bootloader as opposed to directly
    from EFI. These changes should also make it a lot saner to support
    cross-mode 32/64-bit EFI booting in the future. Getting these changes
    into 3.8 means we avoid presenting an inconsistent ABI to bootloaders.

    Other changes are display detection and fixing efivarfs."

    * 'x86-efi-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
    x86, efi: remove attribute check from setup_efi_pci
    x86, build: Dynamically find entry points in compressed startup code
    x86, efi: Fix PCI ROM handing in EFI boot stub, in 32-bit mode
    x86, efi: Fix 32-bit EFI handover protocol entry point
    x86, efi: Fix display detection in EFI boot stub
    x86, boot: Define the 2.12 bzImage boot protocol
    x86/boot: Fix minor fd leakage in tools/relocs.c
    x86, efi: Set runtime_version to the EFI spec revision
    x86, efi: fix 32-bit warnings in setup_efi_pci()
    efivarfs: Delete dentry from dcache in efivarfs_file_write()
    efivarfs: Never return ENOENT from firmware
    efi, x86: Pass a proper identity mapping in efi_call_phys_prelog
    efivarfs: Drop link count of the right inode

    Linus Torvalds
     

29 Jan, 2013

1 commit


28 Jan, 2013

1 commit

  • Define the 2.12 bzImage boot protocol: add xloadflags and additional
    fields to allow the command line, initramfs and struct boot_params to
    live above the 4 GiB mark.

    The xloadflags now communicates if this is a 64-bit kernel with the
    legacy 64-bit entry point and which of the EFI handover entry points
    are supported.

    Avoid adding new read flags to loadflags because of claimed
    bootloaders testing the whole byte for == 1 to determine bzImageness
    at least until the issue can be researched further.

    This is based on patches by Yinghai Lu and David Woodhouse.

    Originally-by: Yinghai Lu
    Originally-by: David Woodhouse
    Acked-by: Yinghai Lu
    Acked-by: David Woodhouse
    Acked-by: Matt Fleming
    Signed-off-by: H. Peter Anvin
    Link: http://lkml.kernel.org/r/1359058816-7615-26-git-send-email-yinghai@kernel.org
    Cc: Rob Landley
    Cc: Gokul Caushik
    Cc: Josh Triplett
    Cc: Joe Millenbach

    H. Peter Anvin
     

25 Jan, 2013

1 commit

  • Pull ARM SoC fixes from Olof Johansson:
    "Here's a long-pending fixes pull request for arm-soc (I didn't send
    one in the -rc4 cycle).

    The larger deltas are from:

    - A fixup of error paths in the mvsdio driver

    - Header file move for a driver that hadn't been properly converted
    to multiplatform on i.MX, which was causing build failures when
    included

    - Device tree updates for at91 dealing mostly with their new pinctrl
    setup merged in 3.8 and mistakes in those initial configs

    The rest are the normal mix of small fixes all over the place; sunxi,
    omap, imx, mvebu, etc, etc."

    * tag 'fixes-for-linus2' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (40 commits)
    mfd: vexpress-sysreg: Don't skip initialization on probe
    ARM: vexpress: Enable A7 cores in V2P-CA15_A7's Device Tree
    ARM: vexpress: extend the MPIDR range used for pen release check
    ARM: at91/dts: correct comment in at91sam9x5.dtsi for mii
    ARM: at91/at91_dt_defconfig: add at91sam9n12 SoC to DT defconfig
    ARM: at91/at91_dt_defconfig: remove memory specification to cmdline
    ARM: at91/dts: add macb mii pinctrl config for kizbox
    ARM: at91: rm9200: remake the BGA as default version
    ARM: at91: fix gpios on i2c-gpio for RM9200 DT
    ARM: at91/at91sam9x5 DTS: add SCK USART pins
    ARM: at91/at91sam9x5 DTS: correct wrong PIO BANK values on u(s)arts
    ARM: at91/at91-pinctrl documentation: fix typo and add some details
    ARM: kirkwood: fix missing #interrupt-cells property
    mmc: mvsdio: use devm_ API to simplify/correct error paths.
    clk: mvebu/clk-cpu.c: fix memory leakage
    ARM: OMAP2+: omap4-panda: add UART2 muxing for WiLink shared transport
    ARM: OMAP2+: DT node Timer iteration fix
    ARM: OMAP2+: Fix section warning for omap_init_ocp2scp()
    ARM: OMAP2+: fix build break for omapdrm
    ARM: OMAP2: Fix missing omap2xxx_clkt_vps_late_init function calls
    ...

    Linus Torvalds
     

24 Jan, 2013

2 commits

  • …ck/linux-rcu into core/urgent

    Pull RCU fixes from Paul E. McKenney.

    Signed-off-by: Ingo Molnar <mingo@kernel.org>

    Ingo Molnar
     
  • Before attempting to activate a RAID array, it is checked for sufficient
    redundancy. That is, we make sure that there are not too many failed
    devices - or devices specified for rebuild - to undermine our ability to
    activate the array. The current code performs this check twice - once to
    ensure there were not too many devices specified for rebuild by the user
    ('validate_rebuild_devices') and again after possibly experiencing a failure
    to read the superblock ('analyse_superblocks'). Neither of these checks are
    sufficient. The first check is done properly but with insufficient
    information about the possible failure state of the devices to make a good
    determination if the array can be activated. The second check is simply
    done wrong in the case of RAID10 because it doesn't account for the
    independence of the stripes (i.e. mirror sets). The solution is to use the
    properly written check ('validate_rebuild_devices'), but perform the check
    after the superblocks have been read and we know which devices have failed.
    This gives us one check instead of two and performs it in a location where
    it can be done right.

    Only RAID10 was affected and it was affected in the following ways:
    - the code did not properly catch the condition where a user specified
    a device for rebuild that already had a failed device in the same mirror
    set. (This condition would, however, be caught at a deeper level in MD.)
    - the code triggers a false positive and denies activation when devices in
    independent mirror sets have failed - counting the failures as though they
    were all in the same set.

    The most likely place this error was introduced (or this patch should have
    been included) is in commit 4ec1e369 - first introduced in v3.7-rc1.
    Consequently this fix should also go in v3.7.y, however there is a
    small conflict on the .version in raid_target, so I'll submit a
    separate patch to -stable.

    Cc: stable@vger.kernel.org
    Signed-off-by: Jonathan Brassow
    Signed-off-by: NeilBrown

    Jonathan Brassow
     

23 Jan, 2013

2 commits

  • The relation between PIN_BANK numbers and pio letters wasn't made very
    clear.

    Signed-off-by: Richard Genoud
    Acked-by: Jean-Christophe PLAGNIOL-VILLARD
    Signed-off-by: Nicolas Ferre

    Richard Genoud
     
  • Pull f2fs fixes from Jaegeuk Kim:
    o Support swap file and link generic_file_remap_pages
    o Enhance the bio streaming flow and free section control
    o Major bug fix on recovery routine
    o Minor bug/warning fixes and code cleanups

    * tag 'f2fs-for-3.8-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs: (22 commits)
    f2fs: use _safe() version of list_for_each
    f2fs: add comments of start_bidx_of_node
    f2fs: avoid issuing small bios due to several dirty node pages
    f2fs: support swapfile
    f2fs: add remap_pages as generic_file_remap_pages
    f2fs: add __init to functions in init_f2fs_fs
    f2fs: fix the debugfs entry creation path
    f2fs: add global mutex_lock to protect f2fs_stat_list
    f2fs: remove the blk_plug usage in f2fs_write_data_pages
    f2fs: avoid redundant time update for parent directory in f2fs_delete_entry
    f2fs: remove redundant call to set_blocksize in f2fs_fill_super
    f2fs: move f2fs_balance_fs to punch_hole
    f2fs: add f2fs_balance_fs in several interfaces
    f2fs: revisit the f2fs_gc flow
    f2fs: check return value during recovery
    f2fs: avoid null dereference in f2fs_acl_from_disk
    f2fs: initialize newly allocated dnode structure
    f2fs: update f2fs partition info about SIT/NAT layout
    f2fs: update f2fs document to reflect SIT/NAT layout correctly
    f2fs: remove unneeded INIT_LIST_HEAD at few places
    ...

    Linus Torvalds
     

09 Jan, 2013

3 commits

  • Pull ARM SoC fixes from Olof Johansson:
    "People are back from the holiday breaks, and it shows. Here are a
    bunch of fixes for a number of platforms:
    - A couple of small fixes for Nomadik
    - A larger set of changes for kirkwood/mvebu
    - uart driver selection, dt clocks, gpio-poweroff fixups, a few
    __init annotation fixes and some error handling improvement in
    their xor dma driver.
    - i.MX had a couple of minor fixes (and a critical one for flexcan2
    clock setup)
    - MXS has a small board fix and a framebuffer bugfix
    - A set of fixes for Samsung Exynos, fixing default bootargs and some
    Exynos5440 clock issues
    - A set of OMAP changes including PM fixes and a few sparse warning
    fixups

    All in all a bit more positive code delta than we'd ideally want to
    see here, mostly from the OMAP PM changes, but nothing overly crazy."

    * tag 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (44 commits)
    ARM: clps711x: Fix bad merge of clockevents setup
    ARM: highbank: save and restore L2 cache and GIC on suspend
    ARM: highbank: add a power request clear
    ARM: highbank: fix secondary boot and hotplug
    ARM: highbank: fix typos with hignbank in power request functions
    ARM: dts: fix highbank cpu mpidr values
    ARM: dts: add device_type prop to cpu nodes on Calxeda platforms
    ARM: mx5: Fix MX53 flexcan2 clock
    ARM: OMAP2+: am33xx-hwmod: Fix wrongly terminated am33xx_usbss_mpu_irqs array
    pinctrl: mvebu: make pdma clock on dove mandatory
    ARM: Dove: Add pinctrl clock to DT
    dma: mv_xor: fix error handling for clocks
    dma: mv_xor: fix error handling of mv_xor_channel_add()
    arm: mvebu: Add missing ; for cpu node.
    arm: mvebu: Armada XP MV78230 has only three Ethernet interfaces
    arm: mvebu: Armada XP MV78230 has two cores, not one
    clk: mvebu: Remove inappropriate __init tagging
    ARM: Kirkwood: Use fixed-regulator instead of board gpio call
    ARM: Kirkwood: Fix missing sdio clock
    ARM: Kirkwood: Switch TWSI1 of 88f6282 to DT clock providers
    ...

    Linus Torvalds
     
  • The as-documented rcu_nocb_poll will fail to enable this feature
    for two reasons. (1) there is an extra "s" in the documented
    name which is not in the code, and (2) since it uses module_param,
    it really is expecting a prefix, akin to "rcutree.fanout_leaf"
    and the prefix isn't documented.

    However, there are several reasons why we might not want to
    simply fix the typo and add the prefix:

    1) we'd end up with rcutree.rcu_nocb_poll, and rather probably make
    a change to rcutree.nocb_poll

    2) if we did #1, then the prefix wouldn't be consistent with the
    rcu_nocbs= parameter (i.e. one with, one without prefix)

    3) the use of module_param in a header file is less than desired,
    since it isn't immediately obvious that it will get processed
    via rcutree.c and get the prefix from that (although use of
    module_param_named() could clarify that.)

    4) the implied export of /sys/module/rcutree/parameters/rcu_nocb_poll
    data to userspace via module_param() doesn't really buy us anything,
    as it is read-only and we can tell if it is enabled already without
    it, since there is a printk at early boot telling us so.

    In light of all that, just change it from a module_param() to an
    early_setup() call, and worry about adding it to /sys later on if
    we decide to allow a dynamic setting of it.

    Also change the variable to be tagged as read_mostly, since it
    will only ever be fiddled with at most, once at boot.

    Signed-off-by: Paul Gortmaker
    Signed-off-by: Paul E. McKenney

    Paul Gortmaker
     
  • From Shawn Guo:

    It includes one critical fix - wrong flexcan2 clock will hang system
    when the port gets brought up. The other two are non-critical fixes,
    which are sent together here, since it's still early -rc stage.

    * tag 'imx-fixes-3.8' of git://git.linaro.org/people/shawnguo/linux-2.6:
    ARM: mx5: Fix MX53 flexcan2 clock
    ARM: dts: imx31-bug: Fix manufacturer compatible string
    clk: imx: Remove 'clock-output-names' from the examples

    Olof Johansson
     

08 Jan, 2013

2 commits

  • Pull networking fixes from David Miller:

    1) New sysctl ndisc_notify needs some documentation, from Hanns
    Frederic Sowa.

    2) Netfilter REJECT target doesn't set transport header of SKB
    correctly, from Mukund Jampala.

    3) Forcedeth driver needs to check for DMA mapping failures, from Larry
    Finger.

    4) brcmsmac driver can't use usleep_range while holding locks, use
    udelay instead. From Niels Ole Salscheider.

    5) Fix unregister of netlink bridge multicast database handlers, from
    Vlad Yasevich and Rami Rosen.

    6) Fix checksum calculations in netfilter's ipv6 network prefix
    translation module.

    7) Fix high order page allocation failures in netfilter xt_recent, from
    Eric Dumazet.

    8) mac802154 needs to use netif_rx_ni() instead of netif_rx() because
    mac802154_process_data() can execute in process rather than
    interrupt context. From Alexander Aring.

    9) Fix splice handling of MSG_SENDPAGE_NOTLAST, otherwise we elide one
    tcp_push() too many. From Eric Dumazet and Willy Tarreau.

    10) Fix skb->truesize tracking in XEN netfront driver, from Ian
    Campbell.

    * git://git.kernel.org/pub/scm/linux/kernel/git/davem/net: (46 commits)
    xen/netfront: improve truesize tracking
    ipv4: fix NULL checking in devinet_ioctl()
    tcp: fix MSG_SENDPAGE_NOTLAST logic
    net/ipv4/ipconfig: really display the BOOTP/DHCP server's address.
    ip-sysctl: fix spelling errors
    mac802154: fix NOHZ local_softirq_pending 08 warning
    ipv6: document ndisc_notify in networking/ip-sysctl.txt
    ath9k: Fix Kconfig for ATH9K_HTC
    netfilter: xt_recent: avoid high order page allocations
    netfilter: fix missing dependencies for the NOTRACK target
    netfilter: ip6t_NPT: fix IPv6 NTP checksum calculation
    bridge: add empty br_mdb_init() and br_mdb_uninit() definitions.
    vxlan: allow live mac address change
    bridge: Correctly unregister MDB rtnetlink handlers
    brcmfmac: fix parsing rsn ie for ap mode.
    brcmsmac: add copyright information for Canonical
    rtlwifi: rtl8723ae: Fix warning for unchecked pci_map_single() call
    rtlwifi: rtl8192se: Fix warning for unchecked pci_map_single() call
    rtlwifi: rtl8192de: Fix warning for unchecked pci_map_single() call
    rtlwifi: rtl8192ce: Fix warning for unchecked pci_map_single() call
    ...

    Linus Torvalds
     
  • Pull ACPI and power management fixes from Rafael Wysocki:

    - Removal of some ACPICA code that the kernel will never use from Lv
    Zheng.

    - APEI fix from Adrian Huang.

    - Removal of unnecessary ACPI memory hotplug driver code from Liu
    Jinsong.

    - Minor ACPI power management fixes.

    - ACPI debug code fix from Joe Perches.

    - ACPI fix to make system bus device nodes get the right names.

    - PNP resources handling fixes from Witold Szczeponik.

    - cpuidle fix for a recent regression stalling boot on systems with
    great numbers of CPUs from Daniel Lezcano.

    - cpuidle fixes from Sivaram Nair.

    - intel_idle debug message fix from Youquan Song.

    - cpufreq build regression fix from Larry Finger.

    - cpufreq fix for an obscure initialization race related to statistics
    from Konstantin Khlebnikov.

    - cpufreq change disabling the Longhaul driver by default from Rafał
    Bilski.

    - PM core fix preventing device suspend errors from happening during
    system suspend due to obscure race conditions.

    - PM QoS local variable name cleanup.

    * tag 'pm+acpi-for-3.8-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
    PM: Move disabling/enabling runtime PM to late suspend/early resume
    PM / QoS: Rename local variable in dev_pm_qos_add_ancestor_request()
    ACPI / scan: Do not use dummy HID for system bus ACPI nodes
    cpufreq / governor: Fix problem with cpufreq_ondemand or cpufreq_conservative
    cpufreq / Longhaul: Disable driver by default
    cpufreq / stats: fix race between stats allocation and first usage
    cpuidle: fix lock contention in the idle path
    intel_idle: pr_debug information need separated
    cpuidle / coupled: fix ready counter decrement
    cpuidle: Fix finding state with min power_usage
    PNP: Handle IORESOURCE_BITS in resource allocation
    PNP: Simplify setting of resources
    ACPI / power: Remove useless message from device registering routine
    ACPI / glue: Update DBG macro to include KERN_DEBUG
    ACPI / PM: Do not apply ACPI_SUCCESS() to acpi_bus_get_device() result
    ACPI / memhotplug: remove redundant logic of acpi memory hotadd
    ACPI / APEI: Fix the returned value in erst_dbg_read
    ACPICA: Remove useless mini-C library.

    Linus Torvalds
     

07 Jan, 2013

1 commit


06 Jan, 2013

1 commit

  • Currently, the PM core disables runtime PM for all devices right
    after executing subsystem/driver .suspend() callbacks for them
    and re-enables it right before executing subsystem/driver .resume()
    callbacks for them. This may lead to problems when there are
    two devices such that the .suspend() callback executed for one of
    them depends on runtime PM working for the other. In that case,
    if runtime PM has already been disabled for the second device,
    the first one's .suspend() won't work correctly (and analogously
    for resume).

    To make those issues go away, make the PM core disable runtime PM
    for devices right before executing subsystem/driver .suspend_late()
    callbacks for them and enable runtime PM for them right after
    executing subsystem/driver .resume_early() callbacks for them. This
    way the potential conflitcs between .suspend_late()/.resume_early()
    and their runtime PM counterparts are still prevented from happening,
    but the subtle ordering issues related to disabling/enabling runtime
    PM for devices during system suspend/resume are much easier to avoid.

    Reported-and-tested-by: Jan-Matthias Braun
    Signed-off-by: Rafael J. Wysocki
    Reviewed-by: Ulf Hansson
    Reviewed-by: Kevin Hilman
    Cc: 3.4+

    Rafael J. Wysocki
     

05 Jan, 2013

4 commits

  • Signed-off-by: Carlos Alberto Lopez Perez
    Cc: Rob Landley
    Cc: Larry Finger
    Cc: Neil Horman
    Cc: Mitsuo Hayasaka
    Cc: Tejun Heo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Carlos Alberto Lopez Perez
     
  • Add 3 new variables and sysctls to tune them (by one "next_id" variable
    for messages, semaphores and shared memory respectively). This variable
    can be used to set desired id for next allocated IPC object. By default
    it's equal to -1 and old behaviour is preserved. If this variable is
    non-negative, then desired idr will be extracted from it and used as a
    start value to search for free IDR slot.

    Notes:

    1) this patch doesn't guarantee that the new object will have desired
    id. So it's up to user space how to handle new object with wrong id.

    2) After a sucessful id allocation attempt, "next_id" will be set back
    to -1 (if it was non-negative).

    [akpm@linux-foundation.org: checkpatch fixes]
    Signed-off-by: Stanislav Kinsbursky
    Cc: Serge Hallyn
    Cc: "Eric W. Biederman"
    Cc: Pavel Emelyanov
    Cc: Al Viro
    Cc: KOSAKI Motohiro
    Cc: Michael Kerrisk
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Stanislav Kinsbursky
     
  • Signed-off-by: Stephen Hemminger
    Signed-off-by: David S. Miller

    stephen hemminger
     
  • I slipped in a new sysctl without proper documentation. I would like to
    make up for this now.

    Signed-off-by: Hannes Frederic Sowa
    Signed-off-by: David S. Miller

    Hannes Frederic Sowa
     

04 Jan, 2013

5 commits

  • 'clock-output-names' is not used in any of the dts/dtsi files for i.mx.

    Remove it from the examples, so that the example and the real usage in the
    dtsi files can match.

    Signed-off-by: Fabio Estevam
    Acked-by: Rob Herring
    Signed-off-by: Shawn Guo

    Fabio Estevam
     
  • document to reflect the layout generated by mkfs.f2fs .

    Signed-off-by: Huajun Li
    Signed-off-by: Jaegeuk Kim

    Huajun Li
     
  • Pull driver core __dev* removal patches - take 3 - from Greg Kroah-Hartman:
    "Here are the remaining __dev* removal patches against the 3.8-rc2
    tree. All of these patches were previously sent to the subsystem
    maintainers, most of them were picked up and pushed to you, but there
    were a number that fell through the cracks, and new drivers were added
    during the merge window, so this series cleans up the rest of the
    instances of these markings.

    Third time's the charm...

    Signed-off-by: Greg Kroah-Hartman "

    Fixed up trivial conflict with the pinctrl pull in pinctrl-sirf.c.

    * tag 'driver-core-3.8-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: (54 commits)
    misc: remove __dev* attributes.
    include: remove __dev* attributes.
    Documentation: remove __dev* attributes.
    Drivers: misc: remove __dev* attributes.
    Drivers: block: remove __dev* attributes.
    Drivers: bcma: remove __dev* attributes.
    Drivers: char: remove __dev* attributes.
    Drivers: clocksource: remove __dev* attributes.
    Drivers: ssb: remove __dev* attributes.
    Drivers: dma: remove __dev* attributes.
    Drivers: gpu: remove __dev* attributes.
    Drivers: infinband: remove __dev* attributes.
    Drivers: memory: remove __dev* attributes.
    Drivers: mmc: remove __dev* attributes.
    Drivers: iommu: remove __dev* attributes.
    Drivers: power: remove __dev* attributes.
    Drivers: message: remove __dev* attributes.
    Drivers: macintosh: remove __dev* attributes.
    Drivers: mfd: remove __dev* attributes.
    pstore: remove __dev* attributes.
    ...

    Linus Torvalds
     
  • CONFIG_HOTPLUG is going away as an option. As a result, the __dev*
    markings need to be removed.

    This change removes the use of __devinit, __devexit_p, __devinitdata,
    __devinitconst, and __devexit from the kernel documentation.

    Based on patches originally written by Bill Pemberton, but redone by me
    in order to handle some of the coding style issues better, by hand.

    Cc: Bill Pemberton
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     
  • Pull pinctrl fixes from Linus Walleij:
    "A first round of pinctrl fixes for v3.8:
    - i.MX5 register configuration
    - Swap a kfree to devm_kfree() to avoid memory corruption in the at91
    driver
    - Add the missing device tree binding doc for the SIRF pin controller
    - Enable the SIRF GPIO pull up/down configuration from the device
    tree, it was previously retired from the hard-coded approach.
    - NULL check for the prcm_base in the Nomadik pin controller.
    - Provide the prcm_base from the device tree in the DT boot path for
    the Nomadik pin controller."

    * tag 'pinctrl-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl:
    ARM: ux500: add pinctrl address resources
    pinctrl: nomadik: return if prcm_base is NULL
    pinctrl: sirf: enable GPIO pullup/down configuration from dts
    pinctrl: sirf: add missing DT-binding document
    pinctrl: fix comment mistake
    drivers/pinctrl/pinctrl-at91.c: convert kfree to devm_kfree
    pinctrl: imx5: fix GPIO_8 pad CAN1_RXCAN configuration

    Linus Torvalds
     

02 Jan, 2013

1 commit


26 Dec, 2012

2 commits

  • commit 7bec207427c2efb794 remove sirfsoc_gpio_set_pull function,
    this patches takes the feature back by adding sirf,pullups and
    sirf,pulldowns prop in dts, and the driver will set the GPIO
    pull according to the dts.

    Cc: Arnd Bergmann
    Signed-off-by: Barry Song
    Signed-off-by: Linus Walleij

    Barry Song
     
  • While sending email to Linus for reviewing:
    "pinctrl: sirf: add DT-binding pinmux mapping support"
    https://patchwork.kernel.org/patch/1364361/

    i have included the devicetree/bindings/pinctrl/pinctrl-sirf.txt

    But while sending pull request with commit 056876f6c73406c,
    i missed the document.

    this patch takes the document back.

    Signed-off-by: Barry Song
    Signed-off-by: Linus Walleij

    Barry Song
     

22 Dec, 2012

1 commit

  • Pull watchdog updates from Wim Van Sebroeck:
    "This includes some fixes and code improvements (like
    clk_prepare_enable and clk_disable_unprepare), conversion from the
    omap_wdt and twl4030_wdt drivers to the watchdog framework, addition
    of the SB8x0 chipset support and the DA9055 Watchdog driver and some
    OF support for the davinci_wdt driver."

    * git://www.linux-watchdog.org/linux-watchdog: (22 commits)
    watchdog: mei: avoid oops in watchdog unregister code path
    watchdog: Orion: Fix possible null-deference in orion_wdt_probe
    watchdog: sp5100_tco: Add SB8x0 chipset support
    watchdog: davinci_wdt: add OF support
    watchdog: da9052: Fix invalid free of devm_ allocated data
    watchdog: twl4030_wdt: Change TWL4030_MODULE_PM_RECEIVER to TWL_MODULE_PM_RECEIVER
    watchdog: remove depends on CONFIG_EXPERIMENTAL
    watchdog: Convert dev_printk(KERN_ to dev_(
    watchdog: DA9055 Watchdog driver
    watchdog: omap_wdt: eliminate goto
    watchdog: omap_wdt: delete redundant platform_set_drvdata() calls
    watchdog: omap_wdt: convert to devm_ functions
    watchdog: omap_wdt: convert to new watchdog core
    watchdog: WatchDog Timer Driver Core: fix comment
    watchdog: s3c2410_wdt: use clk_prepare_enable and clk_disable_unprepare
    watchdog: imx2_wdt: Select the driver via ARCH_MXC
    watchdog: cpu5wdt.c: add missing del_timer call
    watchdog: hpwdt.c: Increase version string
    watchdog: Convert twl4030_wdt to watchdog core
    davinci_wdt: preparation for switch to common clock framework
    ...

    Linus Torvalds
     

21 Dec, 2012

7 commits

  • Merge the rest of Andrew's patches for -rc1:
    "A bunch of fixes and misc missed-out-on things.

    That'll do for -rc1. I still have a batch of IPC patches which still
    have a possible bug report which I'm chasing down."

    * emailed patches from Andrew Morton : (25 commits)
    keys: use keyring_alloc() to create module signing keyring
    keys: fix unreachable code
    sendfile: allows bypassing of notifier events
    SGI-XP: handle non-fatal traps
    fat: fix incorrect function comment
    Documentation: ABI: remove testing/sysfs-devices-node
    proc: fix inconsistent lock state
    linux/kernel.h: fix DIV_ROUND_CLOSEST with unsigned divisors
    memcg: don't register hotcpu notifier from ->css_alloc()
    checkpatch: warn on uapi #includes that #include
    mm: cma: WARN if freed memory is still in use
    exec: do not leave bprm->interp on stack
    ...

    Linus Torvalds
     
  • Pull VFS update from Al Viro:
    "fscache fixes, ESTALE patchset, vmtruncate removal series, assorted
    misc stuff."

    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs: (79 commits)
    vfs: make lremovexattr retry once on ESTALE error
    vfs: make removexattr retry once on ESTALE
    vfs: make llistxattr retry once on ESTALE error
    vfs: make listxattr retry once on ESTALE error
    vfs: make lgetxattr retry once on ESTALE
    vfs: make getxattr retry once on an ESTALE error
    vfs: allow lsetxattr() to retry once on ESTALE errors
    vfs: allow setxattr to retry once on ESTALE errors
    vfs: allow utimensat() calls to retry once on an ESTALE error
    vfs: fix user_statfs to retry once on ESTALE errors
    vfs: make fchownat retry once on ESTALE errors
    vfs: make fchmodat retry once on ESTALE errors
    vfs: have chroot retry once on ESTALE error
    vfs: have chdir retry lookup and call once on ESTALE error
    vfs: have faccessat retry once on an ESTALE error
    vfs: have do_sys_truncate retry once on an ESTALE error
    vfs: fix renameat to retry on ESTALE errors
    vfs: make do_unlinkat retry once on ESTALE errors
    vfs: make do_rmdir retry once on ESTALE errors
    vfs: add a flags argument to user_path_parent
    ...

    Linus Torvalds
     
  • This file is already documented in the stable ABI (see commit
    5bbe1ec11fcf).

    Signed-off-by: Davidlohr Bueso
    Cc: Greg KH
    Cc: Mel Gorman
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Davidlohr Bueso
     
  • Remove the documentation for capability.disable. The code supporting
    this parameter was removed with commit 5915eb53861c ("security: remove
    dummy module")

    Signed-off-by: Josh Boyer
    Acked-by: Serge Hallyn
    Cc: Rob Landley
    Cc: Miklos Szeredi
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Josh Boyer
     
  • …/linux-fs into for-linus

    Al Viro
     
  • Removed vmtruncate

    Signed-off-by: Marco Stornelli
    Signed-off-by: Al Viro

    Marco Stornelli
     
  • Pull nfsd update from Bruce Fields:
    "Included this time:

    - more nfsd containerization work from Stanislav Kinsbursky: we're
    not quite there yet, but should be by 3.9.

    - NFSv4.1 progress: implementation of basic backchannel security
    negotiation and the mandatory BACKCHANNEL_CTL operation. See

    http://wiki.linux-nfs.org/wiki/index.php/Server_4.0_and_4.1_issues

    for remaining TODO's

    - Fixes for some bugs that could be triggered by unusual compounds.
    Our xdr code wasn't designed with v4 compounds in mind, and it
    shows. A more thorough rewrite is still a todo.

    - If you've ever seen "RPC: multiple fragments per record not
    supported" logged while using some sort of odd userland NFS client,
    that should now be fixed.

    - Further work from Jeff Layton on our mechanism for storing
    information about NFSv4 clients across reboots.

    - Further work from Bryan Schumaker on his fault-injection mechanism
    (which allows us to discard selective NFSv4 state, to excercise
    rarely-taken recovery code paths in the client.)

    - The usual mix of miscellaneous bugs and cleanup.

    Thanks to everyone who tested or contributed this cycle."

    * 'for-3.8' of git://linux-nfs.org/~bfields/linux: (111 commits)
    nfsd4: don't leave freed stateid hashed
    nfsd4: free_stateid can use the current stateid
    nfsd4: cleanup: replace rq_resused count by rq_next_page pointer
    nfsd: warn on odd reply state in nfsd_vfs_read
    nfsd4: fix oops on unusual readlike compound
    nfsd4: disable zero-copy on non-final read ops
    svcrpc: fix some printks
    NFSD: Correct the size calculation in fault_inject_write
    NFSD: Pass correct buffer size to rpc_ntop
    nfsd: pass proper net to nfsd_destroy() from NFSd kthreads
    nfsd: simplify service shutdown
    nfsd: replace boolean nfsd_up flag by users counter
    nfsd: simplify NFSv4 state init and shutdown
    nfsd: introduce helpers for generic resources init and shutdown
    nfsd: make NFSd service structure allocated per net
    nfsd: make NFSd service boot time per-net
    nfsd: per-net NFSd up flag introduced
    nfsd: move per-net startup code to separated function
    nfsd: pass net to __write_ports() and down
    nfsd: pass net to nfsd_set_nrthreads()
    ...

    Linus Torvalds