13 Dec, 2014

2 commits


19 Oct, 2014

2 commits

  • Pull block layer driver update from Jens Axboe:
    "This is the block driver pull request for 3.18. Not a lot in there
    this round, and nothing earth shattering.

    - A round of drbd fixes from the linbit team, and an improvement in
    asender performance.

    - Removal of deprecated (and unused) IRQF_DISABLED flag in rsxx and
    hd from Michael Opdenacker.

    - Disable entropy collection from flash devices by default, from Mike
    Snitzer.

    - A small collection of xen blkfront/back fixes from Roger Pau Monné
    and Vitaly Kuznetsov"

    * 'for-3.18/drivers' of git://git.kernel.dk/linux-block:
    block: disable entropy contributions for nonrot devices
    xen, blkfront: factor out flush-related checks from do_blkif_request()
    xen-blkback: fix leak on grant map error path
    xen/blkback: unmap all persistent grants when frontend gets disconnected
    rsxx: Remove deprecated IRQF_DISABLED
    block: hd: remove deprecated IRQF_DISABLED
    drbd: use RB_DECLARE_CALLBACKS() to define augment callbacks
    drbd: compute the end before rb_insert_augmented()
    drbd: Add missing newline in resync progress display in /proc/drbd
    drbd: reduce lock contention in drbd_worker
    drbd: Improve asender performance
    drbd: Get rid of the WORK_PENDING macro
    drbd: Get rid of the __no_warn and __cond_lock macros
    drbd: Avoid inconsistent locking warning
    drbd: Remove superfluous newline from "resync_extents" debugfs entry.
    drbd: Use consistent names for all the bi_end_io callbacks
    drbd: Use better variable names

    Linus Torvalds
     
  • Pull core block layer changes from Jens Axboe:
    "This is the core block IO pull request for 3.18. Apart from the new
    and improved flush machinery for blk-mq, this is all mostly bug fixes
    and cleanups.

    - blk-mq timeout updates and fixes from Christoph.

    - Removal of REQ_END, also from Christoph. We pass it through the
    ->queue_rq() hook for blk-mq instead, freeing up one of the request
    bits. The space was overly tight on 32-bit, so Martin also killed
    REQ_KERNEL since it's no longer used.

    - blk integrity updates and fixes from Martin and Gu Zheng.

    - Update to the flush machinery for blk-mq from Ming Lei. Now we
    have a per hardware context flush request, which both cleans up the
    code should scale better for flush intensive workloads on blk-mq.

    - Improve the error printing, from Rob Elliott.

    - Backing device improvements and cleanups from Tejun.

    - Fixup of a misplaced rq_complete() tracepoint from Hannes.

    - Make blk_get_request() return error pointers, fixing up issues
    where we NULL deref when a device goes bad or missing. From Joe
    Lawrence.

    - Prep work for drastically reducing the memory consumption of dm
    devices from Junichi Nomura. This allows creating clone bio sets
    without preallocating a lot of memory.

    - Fix a blk-mq hang on certain combinations of queue depths and
    hardware queues from me.

    - Limit memory consumption for blk-mq devices for crash dump
    scenarios and drivers that use crazy high depths (certain SCSI
    shared tag setups). We now just use a single queue and limited
    depth for that"

    * 'for-3.18/core' of git://git.kernel.dk/linux-block: (58 commits)
    block: Remove REQ_KERNEL
    blk-mq: allocate cpumask on the home node
    bio-integrity: remove the needless fail handle of bip_slab creating
    block: include func name in __get_request prints
    block: make blk_update_request print prefix match ratelimited prefix
    blk-merge: don't compute bi_phys_segments from bi_vcnt for cloned bio
    block: fix alignment_offset math that assumes io_min is a power-of-2
    blk-mq: Make bt_clear_tag() easier to read
    blk-mq: fix potential hang if rolling wakeup depth is too high
    block: add bioset_create_nobvec()
    block: use bio_clone_fast() in blk_rq_prep_clone()
    block: misplaced rq_complete tracepoint
    sd: Honor block layer integrity handling flags
    block: Replace strnicmp with strncasecmp
    block: Add T10 Protection Information functions
    block: Don't merge requests if integrity flags differ
    block: Integrity checksum flag
    block: Relocate bio integrity flags
    block: Add a disk flag to block integrity profile
    block: Add prefix to block integrity profile flags
    ...

    Linus Torvalds
     

16 Oct, 2014

1 commit

  • The Linux kernel coding style guidelines suggest not using typedefs
    for structure types. This patch gets rid of the typedef for
    atiixp_ide_timing.

    The following Coccinelle semantic patch detects the case:

    @tn1@
    type td;
    @@

    typedef struct { ... } td;

    @script:python tf@
    td << tn1.td;
    tdres;
    @@

    coccinelle.tdres = td;

    @@
    type tn1.td;
    identifier tf.tdres;
    @@

    -typedef
    struct
    + tdres
    { ... }
    -td
    ;

    @@
    type tn1.td;
    identifier tf.tdres;
    @@

    -td
    + struct tdres

    Signed-off-by: Himangi Saraogi
    Acked-by: Julia Lawall
    Signed-off-by: David S. Miller

    Himangi Saraogi
     

05 Oct, 2014

1 commit

  • Clear QUEUE_FLAG_ADD_RANDOM in all block drivers that set
    QUEUE_FLAG_NONROT.

    Historically, all block devices have automatically made entropy
    contributions. But as previously stated in commit e2e1a148 ("block: add
    sysfs knob for turning off disk entropy contributions"):
    - On SSD disks, the completion times aren't as random as they
    are for rotational drives. So it's questionable whether they
    should contribute to the random pool in the first place.
    - Calling add_disk_randomness() has a lot of overhead.

    There are more reliable sources for randomness than non-rotational block
    devices. From a security perspective it is better to err on the side of
    caution than to allow entropy contributions from unreliable "random"
    sources.

    Signed-off-by: Mike Snitzer
    Signed-off-by: Jens Axboe

    Mike Snitzer
     

29 Aug, 2014

1 commit

  • The blk_get_request function may fail in low-memory conditions or during
    device removal (even if __GFP_WAIT is set). To distinguish between these
    errors, modify the blk_get_request call stack to return the appropriate
    ERR_PTR. Verify that all callers check the return status and consider
    IS_ERR instead of a simple NULL pointer check.

    For consistency, make a similar change to the blk_mq_alloc_request leg
    of blk_get_request. It may fail if the queue is dead, or the caller was
    unwilling to wait.

    Signed-off-by: Joe Lawrence
    Acked-by: Jiri Kosina [for pktdvd]
    Acked-by: Boaz Harrosh [for osd]
    Reviewed-by: Jeff Moyer
    Signed-off-by: Jens Axboe

    Joe Lawrence
     

06 Aug, 2014

1 commit


22 Jul, 2014

1 commit

  • Pull IDE fixes from David Miller:
    - fix interrupt registry for some Atari IDE chipsets.
    - adjust Kconfig dependencies for x86_32 specific chips.

    * git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide:
    ide: Fix SC1200 dependencies
    ide: Fix CS5520 and CS5530 dependencies
    m68k/atari - ide: do not register interrupt if host->get_lock is set

    Linus Torvalds
     

16 Apr, 2014

1 commit

  • This was used in the olden days, back when onions were proper
    yellow. Basically it mapped to the current buffer to be
    transferred. With highmem being added more than a decade ago,
    most drivers map pages out of a bio, and rq->buffer isn't
    pointing at anything valid.

    Convert old style drivers to just use bio_data().

    For the discard payload use case, just reference the page
    in the bio.

    Signed-off-by: Jens Axboe

    Jens Axboe
     

18 Mar, 2014

2 commits

  • The SC1200 is a SoC based on the Geode GX1 32-bit x86 processor, so
    its drivers are only needed on this architecture, except for build
    testing purpose.

    Signed-off-by: Jean Delvare
    Cc: "David S. Miller"
    Signed-off-by: David S. Miller

    Jean Delvare
     
  • As far as I know, the CS5520 and CS5530 chipsets were only used with
    32-bit x86 Geode processors, so I think their drivers are only needed
    on this architecture, except for build testing purpose.

    While we're here, simplify the dependencies for the CS5535 driver.

    Signed-off-by: Jean Delvare
    Cc: "David S. Miller"
    Signed-off-by: David S. Miller

    Jean Delvare
     

05 Mar, 2014

1 commit

  • On m68k, host->get_lock is used to both lock and register the interrupt
    that the IDE host shares with other device drivers. Registering the
    IDE interrupt handler in ide-probe.c results in duplicating the
    interrupt registered (once via host->get lock, and also via init_irq()),
    and may result in IDE accepting interrupts even when another driver has
    locked the interrupt hardware. This opens the whole locking scheme up
    to races.

    host->get_lock is set on m68k only, so other drivers' behaviour is not
    changed.

    Signed-off-by: Michael Schmitz
    Cc: Geert Uytterhoeven
    Cc: David S. Miller
    Cc: linux-ide@vger.kernel.org
    Signed-off-by: David S. Miller

    Michael Schmitz
     

29 Jan, 2014

2 commits

  • Include appropriate header file include/linux/ide.h in file
    ide-pio-blacklist.c because function ide_scan_pio_blacklist() has it's
    prototype declaration in include/linux/ide.h.

    This eliminates the following warning in ide-pio-blacklist.c:
    drivers/ide/ide-pio-blacklist.c:85:5: warning: no previous prototype for ‘ide_scan_pio_blacklist’ [-Wmissing-prototypes]

    Signed-off-by: Rashika Kheria
    Reviewed-by: Josh Triplett
    Signed-off-by: David S. Miller

    Rashika Kheria
     
  • Include appropriate header file ide-cd.h in ide-cd_verbose.c because
    function ide_cd_log_error() has its prototype declaration in ide-cd.h.
    Also, include linux/ide.h because it contains certain declarations
    necessary for including ide-cd.h.

    This eliminates the following warnings in ide-cd_verbose.c:
    drivers/ide/ide-cd_verbose.c:251:6: warning: no previous prototype for ‘ide_cd_log_error’ [-Wmissing-prototypes]

    Signed-off-by: Rashika Kheria
    Reviewed-by: Josh Triplett
    Signed-off-by: David S. Miller

    Rashika Kheria
     

25 Jan, 2014

1 commit

  • Pull ACPI and power management updates from Rafael Wysocki:
    "As far as the number of commits goes, the top spot belongs to ACPI
    this time with cpufreq in the second position and a handful of PM
    core, PNP and cpuidle updates. They are fixes and cleanups mostly, as
    usual, with a couple of new features in the mix.

    The most visible change is probably that we will create struct
    acpi_device objects (visible in sysfs) for all devices represented in
    the ACPI tables regardless of their status and there will be a new
    sysfs attribute under those objects allowing user space to check that
    status via _STA.

    Consequently, ACPI device eject or generally hot-removal will not
    delete those objects, unless the table containing the corresponding
    namespace nodes is unloaded, which is extremely rare. Also ACPI
    container hotplug will be handled quite a bit differently and cpufreq
    will support CPU boost ("turbo") generically and not only in the
    acpi-cpufreq driver.

    Specifics:

    - ACPI core changes to make it create a struct acpi_device object for
    every device represented in the ACPI tables during all namespace
    scans regardless of the current status of that device. In
    accordance with this, ACPI hotplug operations will not delete those
    objects, unless the underlying ACPI tables go away.

    - On top of the above, new sysfs attribute for ACPI device objects
    allowing user space to check device status by triggering the
    execution of _STA for its ACPI object. From Srinivas Pandruvada.

    - ACPI core hotplug changes reducing code duplication, integrating
    the PCI root hotplug with the core and reworking container hotplug.

    - ACPI core simplifications making it use ACPI_COMPANION() in the
    code "glueing" ACPI device objects to "physical" devices.

    - ACPICA update to upstream version 20131218. This adds support for
    the DBG2 and PCCT tables to ACPICA, fixes some bugs and improves
    debug facilities. From Bob Moore, Lv Zheng and Betty Dall.

    - Init code change to carry out the early ACPI initialization
    earlier. That should allow us to use ACPI during the timekeeping
    initialization and possibly to simplify the EFI initialization too.
    From Chun-Yi Lee.

    - Clenups of the inclusions of ACPI headers in many places all over
    from Lv Zheng and Rashika Kheria (work in progress).

    - New helper for ACPI _DSM execution and rework of the code in
    drivers that uses _DSM to execute it via the new helper. From
    Jiang Liu.

    - New Win8 OSI blacklist entries from Takashi Iwai.

    - Assorted ACPI fixes and cleanups from Al Stone, Emil Goode, Hanjun
    Guo, Lan Tianyu, Masanari Iida, Oliver Neukum, Prarit Bhargava,
    Rashika Kheria, Tang Chen, Zhang Rui.

    - intel_pstate driver updates, including proper Baytrail support,
    from Dirk Brandewie and intel_pstate documentation from Ramkumar
    Ramachandra.

    - Generic CPU boost ("turbo") support for cpufreq from Lukasz
    Majewski.

    - powernow-k6 cpufreq driver fixes from Mikulas Patocka.

    - cpufreq core fixes and cleanups from Viresh Kumar, Jane Li, Mark
    Brown.

    - Assorted cpufreq drivers fixes and cleanups from Anson Huang, John
    Tobias, Paul Bolle, Paul Walmsley, Sachin Kamat, Shawn Guo, Viresh
    Kumar.

    - cpuidle cleanups from Bartlomiej Zolnierkiewicz.

    - Support for hibernation APM events from Bin Shi.

    - Hibernation fix to avoid bringing up nonboot CPUs with ACPI EC
    disabled during thaw transitions from Bjørn Mork.

    - PM core fixes and cleanups from Ben Dooks, Leonardo Potenza, Ulf
    Hansson.

    - PNP subsystem fixes and cleanups from Dmitry Torokhov, Levente
    Kurusa, Rashika Kheria.

    - New tool for profiling system suspend from Todd E Brandt and a
    cpupower tool cleanup from One Thousand Gnomes"

    * tag 'pm+acpi-3.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (153 commits)
    thermal: exynos: boost: Automatic enable/disable of BOOST feature (at Exynos4412)
    cpufreq: exynos4x12: Change L0 driver data to CPUFREQ_BOOST_FREQ
    Documentation: cpufreq / boost: Update BOOST documentation
    cpufreq: exynos: Extend Exynos cpufreq driver to support boost
    cpufreq / boost: Kconfig: Support for software-managed BOOST
    acpi-cpufreq: Adjust the code to use the common boost attribute
    cpufreq: Add boost frequency support in core
    intel_pstate: Add trace point to report internal state.
    cpufreq: introduce cpufreq_generic_get() routine
    ARM: SA1100: Create dummy clk_get_rate() to avoid build failures
    cpufreq: stats: create sysfs entries when cpufreq_stats is a module
    cpufreq: stats: free table and remove sysfs entry in a single routine
    cpufreq: stats: remove hotplug notifiers
    cpufreq: stats: handle cpufreq_unregister_driver() and suspend/resume properly
    cpufreq: speedstep: remove unused speedstep_get_state
    platform: introduce OF style 'modalias' support for platform bus
    PM / tools: new tool for suspend/resume performance optimization
    ACPI: fix module autoloading for ACPI enumerated devices
    ACPI: add module autoloading support for ACPI enumerated devices
    ACPI: fix create_modalias() return value handling
    ...

    Linus Torvalds
     

07 Dec, 2013

2 commits

  • Since drivers/ide/ide-acpi.c is the only remaining user of
    acpi_get_child(), move that function into that file as a static
    routine.

    Signed-off-by: Rafael J. Wysocki

    Rafael J. Wysocki
     
  • Replace direct inclusions of , and
    , which are incorrect, with
    inclusions and remove some inclusions of those files that aren't
    necessary.

    First of all, , and
    should not be included directly from any files that are built for
    CONFIG_ACPI unset, because that generally leads to build warnings about
    undefined symbols in !CONFIG_ACPI builds. For CONFIG_ACPI set,
    includes those files and for CONFIG_ACPI unset it
    provides stub ACPI symbols to be used in that case.

    Second, there are ordering dependencies between those files that always
    have to be met. Namely, it is required that be included
    prior to so that the acpi_pci_root declarations the
    latter depends on are always there. And which provides
    basic ACPICA type declarations should always be included prior to any other
    ACPI headers in CONFIG_ACPI builds. That also is taken care of including
    as appropriate.

    Signed-off-by: Lv Zheng
    Cc: Greg Kroah-Hartman
    Cc: Matthew Garrett
    Cc: Tony Luck
    Cc: "H. Peter Anvin"
    Acked-by: Bjorn Helgaas (drivers/pci stuff)
    Acked-by: Konrad Rzeszutek Wilk (Xen stuff)
    Signed-off-by: Rafael J. Wysocki

    Lv Zheng
     

26 Nov, 2013

1 commit

  • ZTWO_VADDR() converts from physical to virtual I/O addresses, so it should
    return "void __iomem *" instead of "unsigned long".

    This allows to drop several casts, but requires adding a few casts to
    accomodate legacy driver frameworks that store "unsigned long" I/O
    addresses.

    Signed-off-by: Geert Uytterhoeven

    Geert Uytterhoeven
     

21 Nov, 2013

1 commit

  • Pull more ACPI and power management updates from Rafael Wysocki:

    - ACPI-based device hotplug fixes for issues introduced recently and a
    fix for an older error code path bug in the ACPI PCI host bridge
    driver

    - Fix for recently broken OMAP cpufreq build from Viresh Kumar

    - Fix for a recent hibernation regression related to s2disk

    - Fix for a locking-related regression in the ACPI EC driver from
    Puneet Kumar

    - System suspend error code path fix related to runtime PM and runtime
    PM documentation update from Ulf Hansson

    - cpufreq's conservative governor fix from Xiaoguang Chen

    - New processor IDs for intel_idle and turbostat and removal of an
    obsolete Kconfig option from Len Brown

    - New device IDs for the ACPI LPSS (Low-Power Subsystem) driver and
    ACPI-based PCI hotplug (ACPIPHP) cleanup from Mika Westerberg

    - Removal of several ACPI video DMI blacklist entries that are not
    necessary any more from Aaron Lu

    - Rework of the ACPI companion representation in struct device and code
    cleanup related to that change from Rafael J Wysocki, Lan Tianyu and
    Jarkko Nikula

    - Fixes for assigning names to ACPI-enumerated I2C and SPI devices from
    Jarkko Nikula

    * tag 'pm+acpi-2-3.13-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (24 commits)
    PCI / hotplug / ACPI: Drop unused acpiphp_debug declaration
    ACPI / scan: Set flags.match_driver in acpi_bus_scan_fixed()
    ACPI / PCI root: Clear driver_data before failing enumeration
    ACPI / hotplug: Fix PCI host bridge hot removal
    ACPI / hotplug: Fix acpi_bus_get_device() return value check
    cpufreq: governor: Remove fossil comment in the cpufreq_governor_dbs()
    ACPI / video: clean up DMI table for initial black screen problem
    ACPI / EC: Ensure lock is acquired before accessing ec struct members
    PM / Hibernate: Do not crash kernel in free_basic_memory_bitmaps()
    ACPI / AC: Remove struct acpi_device pointer from struct acpi_ac
    spi: Use stable dev_name for ACPI enumerated SPI slaves
    i2c: Use stable dev_name for ACPI enumerated I2C slaves
    ACPI: Provide acpi_dev_name accessor for struct acpi_device device name
    ACPI / bind: Use (put|get)_device() on ACPI device objects too
    ACPI: Eliminate the DEVICE_ACPI_HANDLE() macro
    ACPI / driver core: Store an ACPI device pointer in struct acpi_dev_node
    cpufreq: OMAP: Fix compilation error 'r & ret undeclared'
    PM / Runtime: Fix error path for prepare
    PM / Runtime: Update documentation around probe|remove|suspend
    cpufreq: conservative: set requested_freq to policy max when it is over policy max
    ...

    Linus Torvalds
     

15 Nov, 2013

5 commits

  • The driver core clears the driver data to NULL after device_release
    or on probe failure. Thus, it is not needed to manually clear the
    device driver data to NULL.

    Signed-off-by: Jingoo Han
    Signed-off-by: David S. Miller

    Jingoo Han
     
  • Use module_pci_driver() macro which makes the code smaller and
    simpler.

    Signed-off-by: Jingoo Han
    Signed-off-by: David S. Miller

    Jingoo Han
     
  • Casting the return value which is a void pointer is redundant.
    The conversion from void pointer to any other pointer type is
    guaranteed by the C programming language.

    Signed-off-by: Jingoo Han
    Signed-off-by: David S. Miller

    Jingoo Han
     
  • Since DEVICE_ACPI_HANDLE() is now literally identical to
    ACPI_HANDLE(), replace it with the latter everywhere and drop its
    definition from include/acpi.h.

    Signed-off-by: Rafael J. Wysocki
    Acked-by: Greg Kroah-Hartman

    Rafael J. Wysocki
     
  • Modify struct acpi_dev_node to contain a pointer to struct acpi_device
    associated with the given device object (that is, its ACPI companion
    device) instead of an ACPI handle corresponding to it. Introduce two
    new macros for manipulating that pointer in a CONFIG_ACPI-safe way,
    ACPI_COMPANION() and ACPI_COMPANION_SET(), and rework the
    ACPI_HANDLE() macro to take the above changes into account.
    Drop the ACPI_HANDLE_SET() macro entirely and rework its users to
    use ACPI_COMPANION_SET() instead. For some of them who used to
    pass the result of acpi_get_child() directly to ACPI_HANDLE_SET()
    introduce a helper routine acpi_preset_companion() doing an
    equivalent thing.

    The main motivation for doing this is that there are things
    represented by struct acpi_device objects that don't have valid
    ACPI handles (so called fixed ACPI hardware features, such as
    power and sleep buttons) and we would like to create platform
    device objects for them and "glue" them to their ACPI companions
    in the usual way (which currently is impossible due to the
    lack of valid ACPI handles). However, there are more reasons
    why it may be useful.

    First, struct acpi_device pointers allow of much better type checking
    than void pointers which are ACPI handles, so it should be more
    difficult to write buggy code using modified struct acpi_dev_node
    and the new macros. Second, the change should help to reduce (over
    time) the number of places in which the result of ACPI_HANDLE() is
    passed to acpi_bus_get_device() in order to obtain a pointer to the
    struct acpi_device associated with the given "physical" device,
    because now that pointer is returned by ACPI_COMPANION() directly.
    Finally, the change should make it easier to write generic code that
    will build both for CONFIG_ACPI set and unset without adding explicit
    compiler directives to it.

    Signed-off-by: Rafael J. Wysocki
    Acked-by: Greg Kroah-Hartman
    Tested-by: Mika Westerberg # on Haswell
    Reviewed-by: Mika Westerberg
    Reviewed-by: Aaron Lu # for ATA and SDIO part

    Rafael J. Wysocki
     

12 Nov, 2013

1 commit

  • Pull h8300 platform removal from Guenter Roeck:
    "The patch series has been in -next for more than one relase cycle. I
    did get a number of Acks, and no objections.

    H8/300 has been dead for several years, the kernel for it has not
    compiled for ages, and recent versions of gcc for it are broken.
    Remove support for it"

    * tag 'h8300-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging:
    CREDITS: Add Yoshinori Sato for h8300
    fs/minix: Drop dependency on H8300
    Drop remaining references to H8/300 architecture
    Drop MAINTAINERS entry for H8/300
    watchdog: Drop references to H8300 architecture
    net/ethernet: Drop H8/300 Ethernet driver
    net/ethernet: smsc9194: Drop conditional code for H8/300
    ide: Drop H8/300 driver
    Drop support for Renesas H8/300 (h8300) architecture

    Linus Torvalds
     

11 Nov, 2013

1 commit

  • Pull ARM SoC cleanups from Olof Johansson:
    "This branch contains code cleanups, moves and removals for 3.13.

    Qualcomm msm targets had a bunch of code removal for legacy non-DT
    platforms. Nomadik saw more device tree conversions and cleanup of
    old code. Tegra has some code refactoring, etc.

    One longish patch series from Sebastian Hasselbarth changes the
    init_time hooks and tries to use a generic implementation for most
    platforms, since they were all doing more or less the same things.

    Finally the "shark" platform is removed in this release. It's been
    abandoned for a while and nobody seems to care enough to keep it
    around. If someone comes along and wants to resurrect it, the removal
    can easily be reverted and code brought back.

    Beyond this, mostly a bunch of removals of stale content across the
    board, etc"

    * tag 'cleanup-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (79 commits)
    ARM: gemini: convert to GENERIC_CLOCKEVENTS
    ARM: EXYNOS: remove CONFIG_MACH_EXYNOS[4, 5]_DT config options
    ARM: OMAP3: control: add API for setting IVA bootmode
    ARM: OMAP3: CM/control: move CM scratchpad save to CM driver
    ARM: OMAP3: McBSP: do not access CM register directly
    ARM: OMAP3: clock: add API to enable/disable autoidle for a single clock
    ARM: OMAP2: CM/PM: remove direct register accesses outside CM code
    MAINTAINERS: Add patterns for DTS files for AT91
    ARM: at91: remove init_machine() as default is suitable
    ARM: at91/dt: split sama5d3 peripheral definitions
    ARM: at91/dt: split sam9x5 peripheral definitions
    ARM: Remove temporary sched_clock.h header
    ARM: clps711x: Use linux/sched_clock.h
    MAINTAINERS: Add DTS files to patterns for Samsung platform
    ARM: EXYNOS: remove unnecessary header inclusions from exynos4/5 dt machine file
    ARM: tegra: fix ARCH_TEGRA_114_SOC select sort order
    clk: nomadik: fix missing __init on nomadik_src_init
    ARM: drop explicit selection of HAVE_CLK and CLKDEV_LOOKUP
    ARM: S3C64XX: Kill CONFIG_PLAT_S3C64XX
    ASoC: samsung: Use CONFIG_ARCH_S3C64XX to check for S3C64XX support
    ...

    Linus Torvalds
     

17 Oct, 2013

1 commit


25 Sep, 2013

1 commit


17 Sep, 2013

1 commit


06 Sep, 2013

5 commits


30 Jul, 2013

1 commit


11 Jul, 2013

3 commits

  • Pull IDE updates from David Miller:
    "Just a few small things:

    1) module_platform_driver_probe() conversions from Jingoo Han.

    2) module_pci_driver() conversion from Libo Chen.

    3) PIO size calculation fix from Steven J Hill"

    * git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide:
    ide: Fix IDE PIO size calculation
    drivers/ide/delkin_cb: Convert to module_pci_driver
    ide: gayle: use module_platform_driver_probe()
    ide: tx4939ide: use module_platform_driver_probe()
    ide: tx4938ide: use module_platform_driver_probe()

    Linus Torvalds
     
  • IDE PIO calculates the size wrong when passing the parameter
    "ide-core.nodma=0.0" to the kernel.

    Signed-off-by: Leonid Yegoshin
    Acked-by: Steven J. Hill

    Signed-off-by: Steven J. Hill
    Signed-off-by: David S. Miller

    Steven J. Hill
     
  • use module_pci_driver instead of init/exit, make code clean.

    Signed-off-by: Libo Chen
    Signed-off-by: David S. Miller

    Libo Chen
     

04 Jul, 2013

1 commit

  • Calling dev_set_name with a single paramter causes it to be handled as a
    format string. Many callers are passing potentially dynamic string
    content, so use "%s" in those cases to avoid any potential accidents,
    including wrappers like device_create*() and bdi_register().

    Signed-off-by: Kees Cook
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Kees Cook