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
17 Mar, 2017
1 commit
-
Add kernel-doc comments to the VME driver API and structures. This
documentation will be integrated into the RST documentation in a later
patch.Signed-off-by: Martyn Welch
Signed-off-by: Greg Kroah-Hartman
11 Jan, 2017
1 commit
-
The vme_driver structure currently has a "node" entry. This entry is
never used and it's intended purpose has been lost to the mists of time.Remove the entry from vme_driver to avoid confusion.
Signed-off-by: Martyn Welch
Signed-off-by: Greg Kroah-Hartman
06 Dec, 2016
1 commit
-
The vme_driver structure currently has a "shutdown" entry. This entry is
never used, it lacks the correct parameter (it should be providing a
pointer to the relevant vme_dev struct to even *look* usable), the VME
subsystem currently doesn't provide support for shutdown functions and no
in-tree drivers use it (hardly surprising, given it'd never be called).Remove the entry from vme_driver to avoid confusion.
Signed-off-by: Martyn Welch
Signed-off-by: Greg Kroah-Hartman
31 Aug, 2016
1 commit
-
Make the location monitor callback function prototype more useful by
changing the argument from an integer to a void pointer.All VME bridge drivers were simply passing the location monitor index
(e.g. 0-3) as the argument to these callbacks. It is much more useful
to pass back a pointer to data that the callback-registering driver
cares about.There appear to be no in-kernel callers of vme_lm_attach (or
vme_lme_request for that matter), so this change only affects the VME
subsystem and bridge drivers.This has been tested with Tsi148 hardware, but the CA91Cx42 changes
have only been compiled.Signed-off-by: Aaron Sierra
Acked-by: Martyn Welch
Signed-off-by: Greg Kroah-Hartman
18 Oct, 2015
1 commit
-
Fixes an off by one array size.
Signed-off-by: Dmitry Kalinkin
Signed-off-by: Greg Kroah-Hartman
13 Jun, 2015
1 commit
-
Signed-off-by: Dmitry Kalinkin
Cc: Igor Alekseev
Signed-off-by: Greg Kroah-Hartman
07 Mar, 2015
1 commit
-
We also make sure that user won't be able to reconfigure the window while it is
mmap'ed.Signed-off-by: Dmitry Kalinkin
Cc: Martyn Welch
Cc: Igor Alekseev
Signed-off-by: Greg Kroah-Hartman
04 Dec, 2013
2 commits
-
Traditionally the "get" functions increment the reference count of the
object that is returned, which does not happen with vme_slot_get. The
function vme_slot_get returns the physical VME slot associated with a
particular struct vme_dev. Rename vme_slot_num to avoid any confusion.Signed-off-by: Martyn Welch
Signed-off-by: Greg Kroah-Hartman -
The match function for vme_user is completely wrong. It will blindly bind
against the first VME slot on each bus (at this point that would be just the
first bus as the driver can only handle one bus).The original intention (before some major subsystem changes) was that the
driver bind against the slot to which the bridge was attached in the VME
system and to the bus(es) provided via the "bus" module parameter.To do this cleanly (i.e. without poking arround in the subsystems internal
stuctures) a functionality has been added to provide access to the bus
enumeration.Signed-off-by: Martyn Welch
Signed-off-by: Greg Kroah-Hartman
27 Apr, 2012
1 commit
-
This moves the VME core, VME board drivers, and VME bridge drivers out
of the drivers/staging/vme/ area to drivers/vme/.The VME device drivers have not moved out yet due to some API questions
they are still working through, that should happen soon, hopefully.Cc: Martyn Welch
Cc: Manohar Vanga
Cc: Vincent Bossier
Cc: "Emilio G. Cota"
Signed-off-by: Greg Kroah-Hartman