1. 08 4月, 2017 1 次提交
  2. 07 4月, 2017 10 次提交
  3. 06 4月, 2017 24 次提交
  4. 05 4月, 2017 5 次提交
    • L
      Merge tag 'kbuild-fixes-v4.11' of... · 9f0bffa1
      Linus Torvalds 提交于
      Merge tag 'kbuild-fixes-v4.11' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild
      
      Pull Kbuild fixes from Masahiro Yamada:
      
       - hand-off primary maintainership of Kbuild
      
       - fix build warnings
      
       - fix build error when GCOV is enabled with old compiler
      
       - fix HAVE_ASM_GOTO check when GCC plugin is enabled
      
      * tag 'kbuild-fixes-v4.11' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild:
        gconfig: remove misleading parentheses around a condition
        jump label: fix passing kbuild_cflags when checking for asm goto support
        Kbuild: use cc-disable-warning consistently for maybe-uninitialized
        kbuild: external module build warnings when KBUILD_OUTPUT set and W=1
        MAINTAINERS: add Masahiro Yamada as a Kbuild maintainer
      9f0bffa1
    • L
      selftests: add a generic testsuite for ethernet device · af0e5461
      LABBE Corentin 提交于
      This patch add a generic testsuite for testing ethernet network device driver.
      Signed-off-by: NCorentin Labbe <clabbe.montjoie@gmail.com>
      Tested-by: NAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      af0e5461
    • D
      Merge branch 'rtnetlink-event-type' · 2e507e24
      David S. Miller 提交于
      Vladislav Yasevich says:
      
      ====================
      rtnetlink: Updates to rtnetlink_event()
      
      This series came out of the conversation that started as a result
      my first attempt to add netdevice event info to netlink messages.
      
      This series converts event processing to a 'white list', where
      we explicitely permit events to generate netlink messages.  This
      is meant to make people take a closer look and determine wheter
      these events should really trigger netlink messages.
      
      I am also adding a V2 of my patch to add event type to the netlink
      message.  This version supports all events that we currently generate.
      
      I will also update my patch to iproute that will show this data
      through 'ip monitor'.
      
      I actually need the ability to trap NETDEV_NOTIFY_PEERS event
      (as well as possible NETDEV_RESEND_IGMP) to support hanlding of
      macvtap on top of bonding.  I hope others will also find this info usefull.
      
      V2: Added missed events (from David Ahern)
      ====================
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2e507e24
    • V
      rtnl: Add support for netdev event to link messages · def12888
      Vlad Yasevich 提交于
      When netdev events happen, a rtnetlink_event() handler will send
      messages for every event in it's white list.  These messages contain
      current information about a particular device, but they do not include
      the iformation about which event just happened.  The consumer of
      the message has to try to infer this information.  In some cases
      (ex: NETDEV_NOTIFY_PEERS), that is not possible.
      
      This patch adds a new extension to RTM_NEWLINK message called IFLA_EVENT
      that would have an encoding of the which event triggered this
      message.  This would allow the the message consumer to easily determine
      if it is interested in a particular event or not.
      Signed-off-by: NVladislav Yasevich <vyasevic@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      def12888
    • V
      rtnetlink: Convert rtnetlink_event to white list · 5138e86f
      Vlad Yasevich 提交于
      The rtnetlink_event currently functions as a blacklist where
      we block cerntain netdev events from being sent to user space.
      As a result, events have been added to the system that userspace
      probably doesn't care about.
      
      This patch converts the implementation to the white list so that
      newly events would have to be specifically added to the list to
      be sent to userspace.  This would force new event implementers to
      consider whether a given event is usefull to user space or if it's
      just a kernel event.
      Signed-off-by: NVladislav Yasevich <vyasevic@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5138e86f