Permalink
Commits on Jun 19, 2014
  1. Bluetooth: Load Connection Parameters Command

    This patch introduces the Load Connection Parameters command to
    Management Interface. This command is used to inform the kernel
    what connection parameters should be used during connection
    establishment.
    
    This command is only supported on controllers with LE support and
    it can be issued while in power on or off mode. Finally, it only
    accepts connection parameters from device with identity address.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 21, 2014
  2. Bluetooth: Remove auto_connect from hci_conn_params

    This patch removes the auto_connect option from strcut hci_conn_params
    as well as all helper functions. Auto connection is now handled by
    le_auto_conn list so we can safely remove it.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 22, 2014
  3. Bluetooth: Store auto connect information in le_auto_connect list

    This patch changes the auto connect infrastructure so hdev->le_auto_
    conn is used instead of hdev->le_conn_params list. Besides that, since
    we now use le_auto_connect list we should delete auto connect
    information during unpair.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 22, 2014
Commits on Jun 17, 2014
  1. Bluetooth: Introduce hdev->le_auto_connect list

    This patch simply adds a linked list to hdev and some helper functions
    that perform basic operations such as add, delete, lookup and clear.
    
    The hdev->le_auto_connect list will store the device addresses the
    kernel should autonomously connect to.
    
    This new linked list is needed because we want to remove the auto_connect
    option from struct hci_conn_params, therefore we cannot rely on hdev->
    le_conn_params list anymore.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 22, 2014
  2. Bluetooth: Extend LE connection parameters infrastructure

    This patch extends connection parameters infrastructure (struct hci_
    conn_params and helper functions) to take into consideration the
    slave latency and supervision timeout parameters as well.
    
    This way, the user will be able to specify those parameters besides
    the minimum and maximum interval parameters.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 21, 2014
  3. Bluetooth: Export supervision timeout parameter

    This patch exports the supervision timeout parameter through Bluetooth
    debugfs interface. We already export minimum/maximum connection interval
    and latency parameters so it makes sense to also export the supervision
    timeout parameter.
    
    The default value is 0x002a and it may be changed by writing the new
    value in conn_supervision_timeout file. The acceptable values range
    from 0x000a to 0x0c80 according described in Core 4.1, Vol 2, 7.8.12.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed Apr 15, 2014
  4. Bluetooth: Export slave latency parameter

    This patch exports slave latency parameter through Bluetooth debugfs
    interface.  We already export minimum and maximum connection interval
    parameters so it makes sense to also export slave latency parameter.
    
    The default value is 0 and it may be changed by writing the new
    value in conn_latenty file. The acceptable values range from 0x0000
    to 0x01F3, according described in Core 4.1, Vol 2, 7.8.12.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed Apr 15, 2014
  5. Bluetooth: Remove min/max connection interval from hci_conn

    The minimum and maximum connection interval values are reported
    to user through a mgmt event (this event is sent during Connection
    Parameter Update Procedure). Besides that, hci_conn already keeps
    track of connection parameters values currently in use. That being
    said, there is no reason to save minimum and maximum connection
    interval values in hci_conn.
    
    Therefore, this patch removes the minimum and maximum connection
    interval from struct hci_conn. Since they are removed, this patch
    also moves the connection parameters lookup to hci_req_add_le_
    create_conn().
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 21, 2014
  6. Bluetooth: Add LE Conn Update Complete Event handler

    This patch adds a handler for LE Conn Update Complete Event. When such
    event occurs, we should update the connection parameters in hci_conn
    object.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 20, 2014
Commits on Jun 16, 2014
  1. Bluetooth: Save connection parameters in hci_conn

    This patch saves the connection interval, latency and supervision
    timeout parameters to hci_conn. This way, we are able to track what
    values are being currently used in a given connection.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 20, 2014
  2. Bluetooth: Introduce "New Connection Parameter" Event

    This patch introduces a new Mgmt event called "New Connection Parameter".
    This event indicates to userspace the connection parameters values the
    remote device requested.
    
    The user may store these values and load them into kernel (an upcoming
    patch will introduce a Mgmt command to do that). This way, next time a
    connection is established to that device, the kernel will use those
    parameters values instead of the default ones.
    
    This event is sent when the remote device requests new connection
    parameters through Link Layer or L2CAP connection parameter update
    procedures.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 21, 2014
  3. Bluetooth: Move is_identity_address() to hci_core.h

    This patch adds the prefix hci_ to is_identity_address() helper and
    moves it to hci_core.h so it can be reused in other files.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed Jun 16, 2014
  4. Bluetooth: Connection Parameter Update Procedure

    This patch adds support for LE Connection Parameters Request Link
    Layer control procedure introduced in Core spec 4.1. This procedure
    allows a Peripheral or Central to update the Link Layer connection
    parameters of an established connection.
    
    Regarding the acceptance of connection parameters, the LL procedure
    follows the same approach of L2CAP procedure (see l2cap_conn_param_
    update_req function). We accept any connection parameters values as
    long as they are within the valid range.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 19, 2014
  5. Bluetooth: Connection parameters check helper

    This patch renames l2cap_check_conn_param() to hci_check_conn_params()
    and moves it to hci_core.h so it can reused in others files. This helper
    will be reused in the next patch.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed May 19, 2014
  6. Bluetooth: Use macro instead of hard-coded value

    This patch replaces the hard-coded value in hci_bdaddr_is_rpa() helper
    by the corresponding macro ADDR_LE_DEV_RANDOM.
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed Jun 16, 2014
  7. Bluetooth: Use BT_DBG in create_le_conn_complete()

    Controller may send error for any command for any reason. It doesn't
    mean we have a error in the system. For that reason, it makes sense to
    use BT_DBG instead of BT_ERR to log messages in create_le_conn_
    complete()
    
    Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
    Andre Guedes committed Mar 10, 2014
Commits on Jun 13, 2014
  1. @holtmann

    Bluetooth: Use explicit header and body length for L2CAP SKB allocation

    When allocating the L2CAP SKB for transmission, provide the upper layers
    with a clear distinction on what is the header and what is the body
    portion of the SKB.
    
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    holtmann committed Jun 8, 2014
  2. @holtmann

    Bluetooth: Shrink size of struct l2cap_ctrl fields

    The struct l2cap_ctrl fields are wasting an unsigned int when all the
    bits can fit into an __u8 field.
    
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    holtmann committed Jun 8, 2014
  3. @holtmann

    Bluetooth: Assign L2CAP socket priority when allocating SKB

    The SKB for L2CAP sockets are all allocated in a central callback
    in the socket support. Instead of having to pass around the socket
    priority all the time, assign it to skb->priority when actually
    allocating the SKB.
    
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    holtmann committed Jun 5, 2014
  4. @holtmann

    Bluetooth: Use const for struct l2cap_ops field

    The struct l2cap_ops field should not allow any modifications and thus
    it is better declared as const.
    
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    holtmann committed Jun 8, 2014
  5. @adam8157 @holtmann

    Bluetooth: ath3k: reduce pipe setting times in ath3k_load_fwfile()

    Invoking usb_sndbulkpipe() on same pipe for same purpose only once is
    enough.
    
    Signed-off-by: Adam Lee <adam8157@gmail.com>
    Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
    adam8157 committed with holtmann Jun 5, 2014
  6. @MarcinKraglak @holtmann

    Bluetooth: Allow change security level on ATT_CID in slave role

    Kernel supports SMP Security Request so don't block increasing security
    when we are slave.
    
    Signed-off-by: Marcin Kraglak <marcin.kraglak@tieto.com>
    Acked-by: Johan Hedberg <johan.hedberg@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org
    MarcinKraglak committed with holtmann Jun 13, 2014
  7. @jhedberg @holtmann

    Bluetooth: Fix locking of hdev when calling into SMP code

    The SMP code expects hdev to be unlocked since e.g. crypto functions
    will try to (re)lock it. Therefore, we need to release the lock before
    calling into smp.c from mgmt.c. Without this we risk a deadlock whenever
    the smp_user_confirm_reply() function is called.
    
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    Tested-by: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org
    jhedberg committed with holtmann Jun 13, 2014
  8. @holtmann

    Bluetooth: Fix deadlock in l2cap_conn_del()

    A deadlock occurs when PDU containing invalid SMP opcode is received on
    Security Manager Channel over LE link and conn->pending_rx_work worker
    has not run yet.
    
    When LE link is created l2cap_conn_ready() is called and before
    returning it schedules conn->pending_rx_work worker to hdev->workqueue.
    Incoming data to SMP fixed channel is handled by l2cap_recv_frame()
    which calls smp_sig_channel() to handle the SMP PDU. If
    smp_sig_channel() indicates failure l2cap_conn_del() is called to delete
    the connection. When deleting the connection, l2cap_conn_del() purges
    the pending_rx queue and calls flush_work() to wait for the
    pending_rx_work worker to complete.
    
    Since incoming data is handled by a worker running from the same
    workqueue as the pending_rx_work is being scheduled on, we will deadlock
    on waiting for pending_rx_work to complete.
    
    This patch fixes the deadlock by calling cancel_work_sync() instead of
    flush_work().
    
    Signed-off-by: Jukka Taimisto <jtt@codenomicon.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org
    Jukka Taimisto committed with holtmann Jun 12, 2014
  9. @jhedberg @holtmann

    Bluetooth: Reuse hci_stop_discovery function when cleaning up HCI state

    When cleaning up the HCI state as part of the power-off procedure we can
    reuse the hci_stop_discovery() function instead of explicitly sending
    HCI command related to discovery. The added benefit of this is that it
    takes care of canceling name resolving and inquiry which were not
    previously covered by the code.
    
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org
    jhedberg committed with holtmann Jun 10, 2014
  10. @jhedberg @holtmann

    Bluetooth: Refactor discovery stopping into its own function

    We'll need to reuse the same logic for stopping discovery also when
    cleaning up HCI state when powering off. This patch refactors the code
    out to its own function that can later (in a subsequent patch) be used
    also for the power off case.
    
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org
    jhedberg committed with holtmann Jun 10, 2014
  11. @jhedberg @holtmann

    Bluetooth: Fix indicating discovery state when canceling inquiry

    When inquiry is canceled through the HCI_Cancel_Inquiry command there is
    no Inquiry Complete event generated. Instead, all we get is the command
    complete for the HCI_Inquiry_Cancel command. This means that we must
    call the hci_discovery_set_state() function from the respective command
    complete handler in order to ensure that user space knows the correct
    discovery state.
    
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org
    jhedberg committed with holtmann Jun 10, 2014
  12. @jhedberg @holtmann

    Bluetooth: Fix setting correct authentication information for SMP STK

    When we store the STK in slave role we should set the correct
    authentication information for it. If the pairing is producing a HIGH
    security level the STK is considered authenticated, and otherwise it's
    considered unauthenticated. This patch fixes the value passed to the
    hci_add_ltk() function when adding the STK on the slave side.
    
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    Tested-by: Marcin Kraglak <marcin.kraglak@tieto.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org
    jhedberg committed with holtmann Jun 10, 2014
  13. @jhedberg @holtmann

    Bluetooth: Add clarifying comment for conn->auth_type

    When responding to an IO capability request when we're the initiators of
    the pairing we will not yet have the remote IO capability information.
    Since the conn->auth_type variable is treated as an "absolute"
    requirement instead of a hint of what's needed later in the user
    confirmation request handler it's important that it doesn't have the
    MITM bit set if there's any chance that the remote device doesn't have
    the necessary IO capabilities.
    
    This patch adds a clarifying comment so that conn->auth_type is left
    untouched in this scenario.
    
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    jhedberg committed with holtmann Jun 9, 2014
  14. @jhedberg @holtmann

    Bluetooth: Fix SSP acceptor just-works confirmation without MITM

    From the Bluetooth Core Specification 4.1 page 1958:
    
    "if both devices have set the Authentication_Requirements parameter to
    one of the MITM Protection Not Required options, authentication stage 1
    shall function as if both devices set their IO capabilities to
    DisplayOnly (e.g., Numeric comparison with automatic confirmation on
    both devices)"
    
    So far our implementation has done user confirmation for all just-works
    cases regardless of the MITM requirements, however following the
    specification to the word means that we should not be doing confirmation
    when neither side has the MITM flag set.
    
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    Tested-by: Szymon Janc <szymon.janc@tieto.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org
    jhedberg committed with holtmann Jun 9, 2014
  15. @jhedberg @holtmann

    Bluetooth: Fix check for connection encryption

    The conn->link_key variable tracks the type of link key in use. It is
    set whenever we respond to a link key request as well as when we get a
    link key notification event.
    
    These two events do not however always guarantee that encryption is
    enabled: getting a link key request and responding to it may only mean
    that the remote side has requested authentication but not encryption. On
    the other hand, the encrypt change event is a certain guarantee that
    encryption is enabled. The real encryption state is already tracked in
    the conn->link_mode variable through the HCI_LM_ENCRYPT bit.
    
    This patch fixes a check for encryption in the hci_conn_auth function to
    use the proper conn->link_mode value and thereby eliminates the chance
    of a false positive result.
    
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org
    jhedberg committed with holtmann Jun 10, 2014
  16. @jhedberg @holtmann

    Bluetooth: Fix incorrectly overriding conn->src_type

    The src_type member of struct hci_conn should always reflect the address
    type of the src_member. It should never be overridden. There is already
    code in place in the command status handler of HCI_LE_Create_Connection
    to copy the right initiator address into conn->init_addr_type.
    
    Without this patch, if privacy is enabled, we will send the wrong
    address type in the SMP identity address information PDU (it'll e.g.
    contain our public address but a random address type).
    
    Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org
    jhedberg committed with holtmann Jun 5, 2014
Commits on Jun 12, 2014
  1. @torvalds

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next

    Pull networking updates from David Miller:
    
     1) Seccomp BPF filters can now be JIT'd, from Alexei Starovoitov.
    
     2) Multiqueue support in xen-netback and xen-netfront, from Andrew J
        Benniston.
    
     3) Allow tweaking of aggregation settings in cdc_ncm driver, from Bjørn
        Mork.
    
     4) BPF now has a "random" opcode, from Chema Gonzalez.
    
     5) Add more BPF documentation and improve test framework, from Daniel
        Borkmann.
    
     6) Support TCP fastopen over ipv6, from Daniel Lee.
    
     7) Add software TSO helper functions and use them to support software
        TSO in mvneta and mv643xx_eth drivers.  From Ezequiel Garcia.
    
     8) Support software TSO in fec driver too, from Nimrod Andy.
    
     9) Add Broadcom SYSTEMPORT driver, from Florian Fainelli.
    
    10) Handle broadcasts more gracefully over macvlan when there are large
        numbers of interfaces configured, from Herbert Xu.
    
    11) Allow more control over fwmark used for non-socket based responses,
        from Lorenzo Colitti.
    
    12) Do TCP congestion window limiting based upon measurements, from Neal
        Cardwell.
    
    13) Support busy polling in SCTP, from Neal Horman.
    
    14) Allow RSS key to be configured via ethtool, from Venkata Duvvuru.
    
    15) Bridge promisc mode handling improvements from Vlad Yasevich.
    
    16) Don't use inetpeer entries to implement ID generation any more, it
        performs poorly, from Eric Dumazet.
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next: (1522 commits)
      rtnetlink: fix userspace API breakage for iproute2 < v3.9.0
      tcp: fixing TLP's FIN recovery
      net: fec: Add software TSO support
      net: fec: Add Scatter/gather support
      net: fec: Increase buffer descriptor entry number
      net: fec: Factorize feature setting
      net: fec: Enable IP header hardware checksum
      net: fec: Factorize the .xmit transmit function
      bridge: fix compile error when compiling without IPv6 support
      bridge: fix smatch warning / potential null pointer dereference
      via-rhine: fix full-duplex with autoneg disable
      bnx2x: Enlarge the dorq threshold for VFs
      bnx2x: Check for UNDI in uncommon branch
      bnx2x: Fix 1G-baseT link
      bnx2x: Fix link for KR with swapped polarity lane
      sctp: Fix sk_ack_backlog wrap-around problem
      net/core: Add VF link state control policy
      net/fsl: xgmac_mdio is dependent on OF_MDIO
      net/fsl: Make xgmac_mdio read error message useful
      net_sched: drr: warn when qdisc is not work conserving
      ...
    torvalds committed Jun 12, 2014
  2. @torvalds

    Merge tag 'dm-3.16-changes' of git://git.kernel.org/pub/scm/linux/ker…

    …nel/git/device-mapper/linux-dm
    
    Pull device mapper updates from Mike Snitzer:
     "This pull request is later than I'd have liked because I was waiting
      for some performance data to help finally justify sending the
      long-standing dm-crypt cpu scalability improvements upstream.
    
      Unfortunately we came up short, so those dm-crypt changes will
      continue to wait, but it seems we're not far off.
    
       . Add dm_accept_partial_bio interface to DM core to allow DM targets
         to only process a portion of a bio, the remainder being sent in the
         next bio.  This enables the old dm snapshot-origin target to only
         split write bios on chunk boundaries, read bios are now sent to the
         origin device unchanged.
    
       . Add DM core support for disabling WRITE SAME if the underlying SCSI
         layer disables it due to command failure.
    
       . Reduce lock contention in DM's bio-prison.
    
       . A few small cleanups and fixes to dm-thin and dm-era"
    
    * tag 'dm-3.16-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm:
      dm thin: update discard_granularity to reflect the thin-pool blocksize
      dm bio prison: implement per bucket locking in the dm_bio_prison hash table
      dm: remove symbol export for dm_set_device_limits
      dm: disable WRITE SAME if it fails
      dm era: check for a non-NULL metadata object before closing it
      dm thin: return ENOSPC instead of EIO when error_if_no_space enabled
      dm thin: cleanup noflush_work to use a proper completion
      dm snapshot: do not split read bios sent to snapshot-origin target
      dm snapshot: allocate a per-target structure for snapshot-origin target
      dm: introduce dm_accept_partial_bio
      dm: change sector_count member in clone_info from sector_t to unsigned
    torvalds committed Jun 12, 2014
  3. @torvalds

    Merge tag 'pci-v3.16-changes-2' of git://git.kernel.org/pub/scm/linux…

    …/kernel/git/helgaas/pci
    
    Pull more PCI updates from Bjorn Helgaas:
     "Here are some more things I'd like to see in v3.16-rc1:
    
       - DMA alias iterator, part of some work to fix IOMMU issues
       - MVEBU, Tegra, DesignWare changes that I forgot to include before
       - Some whitespace code cleanup
    
      Details:
    
      IOMMU
        - Add DMA alias iterator (Alex Williamson)
        - Add DMA alias quirks for ASMedia, ITE, Tundra bridges (Alex Williamson)
        - Add DMA alias quirks for Marvell, Ricoh devices (Alex Williamson)
        - Add DMA alias quirk for HighPoint devices (Jérôme Carretero)
    
      MSI
        - Fix leak in free_msi_irqs() (Alexei Starovoitov)
    
      Marvell MVEBU
        - Remove unnecessary use of 'conf_lock' spinlock (Andrew Murray)
        - Avoid setting an undefined window size (Jason Gunthorpe)
        - Allow several windows with the same target/attribute (Thomas Petazzoni)
        - Split PCIe BARs into multiple MBus windows when needed (Thomas Petazzoni)
        - Fix off-by-one in the computed size of the mbus windows (Willy Tarreau)
    
      NVIDIA Tegra
        - Use new OF interrupt mapping when possible (Lucas Stach)
    
      Synopsys DesignWare
        - Remove unnecessary use of 'conf_lock' spinlock (Andrew Murray)
        - Use new OF interrupt mapping when possible (Lucas Stach)
        - Split Exynos and i.MX bindings (Lucas Stach)
        - Fix comment for setting number of lanes (Mohit Kumar)
        - Fix iATU programming for cfg1, io and mem viewport (Mohit Kumar)
    
      Miscellaneous
        - EXPORT_SYMBOL cleanup (Ryan Desfosses)
        - Whitespace cleanup (Ryan Desfosses)
        - Merge multi-line quoted strings (Ryan Desfosses)"
    
    * tag 'pci-v3.16-changes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci: (21 commits)
      PCI: Add function 1 DMA alias quirk for HighPoint RocketRaid 642L
      PCI/MSI: Fix memory leak in free_msi_irqs()
      PCI: Merge multi-line quoted strings
      PCI: Whitespace cleanup
      PCI: Move EXPORT_SYMBOL so it immediately follows function/variable
      PCI: Add bridge DMA alias quirk for ITE bridge
      PCI: designware: Split Exynos and i.MX bindings
      PCI: Add bridge DMA alias quirk for ASMedia and Tundra bridges
      PCI: Add support for PCIe-to-PCI bridge DMA alias quirks
      PCI: Add function 1 DMA alias quirk for Marvell devices
      PCI: Add function 0 DMA alias quirk for Ricoh devices
      PCI: Add support for DMA alias quirks
      PCI: Convert pci_dev_flags definitions to bit shifts
      PCI: Add DMA alias iterator
      PCI: mvebu: Use '%pa' for printing 'phys_addr_t' type
      PCI: mvebu: Remove unnecessary use of 'conf_lock' spinlock
      PCI: designware: Remove unnecessary use of 'conf_lock' spinlock
      PCI: designware: Use new OF interrupt mapping when possible
      PCI: designware: Fix iATU programming for cfg1, io and mem viewport
      PCI: designware: Fix comment for setting number of lanes
      ...
    torvalds committed Jun 12, 2014