28 Mar, 2019

1 commit


12 Feb, 2019

1 commit


02 Nov, 2017

1 commit

  • Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license of the kernel, which is GPL version 2.

    Update the files which contain no license information with the 'GPL-2.0'
    SPDX license identifier. The SPDX identifier is a legally binding
    shorthand, which can be used instead of the full boiler plate text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart and
    Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset of
    the use cases:
    - file had no licensing information it it.
    - file was a */uapi/* one with no licensing information in it,
    - file was a */uapi/* one with existing licensing information,

    Further patches will be generated in subsequent months to fix up cases
    where non-standard license headers were used, and references to license
    had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied to
    a file was done in a spreadsheet of side by side results from of the
    output of two independent scanners (ScanCode & Windriver) producing SPDX
    tag:value files created by Philippe Ombredanne. Philippe prepared the
    base worksheet, and did an initial spot review of a few 1000 files.

    The 4.13 kernel was the starting point of the analysis with 60,537 files
    assessed. Kate Stewart did a file by file comparison of the scanner
    results in the spreadsheet to determine which SPDX license identifier(s)
    to be applied to the file. She confirmed any determination that was not
    immediately clear with lawyers working with the Linux Foundation.

    Criteria used to select files for SPDX license identifier tagging was:
    - Files considered eligible had to be source code files.
    - Make and config files were included as candidates if they contained >5
    lines of source
    - File already had some variant of a license header in it (even if
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

06 Dec, 2016

1 commit

  • Enable non-blocking receive for drivers on mei bus, this allows checking
    for data availability by mei client drivers. This is most effective for
    fixed address clients, that lacks flow control.

    This function adds new API function mei_cldev_recv_nonblock(), it
    retuns -EGAIN if function will block.

    Signed-off-by: Alexander Usyskin
    Signed-off-by: Tomas Winkler
    Signed-off-by: Greg Kroah-Hartman

    Alexander Usyskin
     

17 Nov, 2016

1 commit


28 Oct, 2016

2 commits


21 Sep, 2015

4 commits


04 Aug, 2015

4 commits

  • Enable drivers on mei client bus to subscribe
    to asynchronous event notifications.
    Introduce events_mask to the existing callback infrastructure
    so it is possible to handle both RX and event notification.

    Signed-off-by: Alexander Usyskin
    Signed-off-by: Tomas Winkler
    Signed-off-by: Greg Kroah-Hartman

    Alexander Usyskin
     
  • Split the device registration into allocation and device struct
    initialization, device setup, and the final device registration.
    This why it is possible to run fixups and quirks during the setup stage
    on an initialized device. Each fixup routine effects do_match flag.
    If the flag is set to false at the end the device won't be
    registered on the bus.

    Signed-off-by: Tomas Winkler
    Signed-off-by: Greg Kroah-Hartman

    Tomas Winkler
     
  • Instead of holding the list of host clients (me_cl)
    we want to keep the list me client devices (mei_cl_device)
    This way we can create host to me client connection only when needed.
    Add list head to mei_cl_device and cl_bus_lock
    Add bus_added flag to the me client (mei_me_client) to track if
    the appropriate mei_cl_device was already created and is_added
    flag to mei_cl_device to track if it was already added to the device
    list across the bus rescans

    Signed-off-by: Tomas Winkler
    Signed-off-by: Greg Kroah-Hartman

    Tomas Winkler
     
  • Add reference to the bus device (mei_device) for easier access.
    To ensures that referencing cldev->bus is valid during cldev life time
    we increase the bus ref counter on a client device creation and drop it
    on the device release.

    Signed-off-by: Tomas Winkler
    Signed-off-by: Greg Kroah-Hartman

    Tomas Winkler
     

25 May, 2015

1 commit


12 Jan, 2015

1 commit


29 Sep, 2014

1 commit


09 Apr, 2013

1 commit

  • It should be left to the drivers to enable and disable the device on the
    MEI bus when e.g getting probed.
    For drivers to be able to safely call the enable and disable hooks, the
    mei_cl_ops must be set before it's probed and thus this should happen
    before registering the device on the MEI bus. Hence the mei_cl_add_device()
    prototype change.

    Signed-off-by: Samuel Ortiz
    Signed-off-by: Tomas Winkler
    Signed-off-by: Greg Kroah-Hartman

    Samuel Ortiz
     

29 Mar, 2013

4 commits