sascha/workload-automation
1
0
Fork 0
mirror of https://github.com/ARM-software/workload-automation.git synced 2025-09-02 03:12:34 +01:00
Code Issues Releases Wiki Activity

doc: Apply it's/its grammar pedantry

Browse Source
This commit is contained in:
Brendan Jackman
2016-01-14 12:05:49 +00:00
parent dc5cf6d7b8
commit 2ae8c6073f
9 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
wlauto/core/configuration.py
View File

@@ -425,7 +425,7 @@ class RunConfiguration(object):
is validated (to make sure there are no missing settings, etc).
- Extensions are loaded through the run config object, which instantiates
them with appropriate parameters based on the "raw" config collected earlier. When an
Extension is instantiated in such a way, it's config is "officially" added to run configuration
Extension is instantiated in such a way, its config is "officially" added to run configuration
tracked by the run config object. Raw config is discarded at the end of the run, so
that any config that wasn't loaded in this way is not recoded (as it was not actually used).
- Extension parameters a validated individually (for type, value ranges, etc) as they are

2
wlauto/core/device.py
View File

@@ -174,7 +174,7 @@ class Device(Extension):
description="""
This is a list indicating the cluster affinity of the CPU cores,
each element correponding to the cluster ID of the core coresponding
to it's index. E.g. ``[0, 0, 1]`` indicates that cpu0 and cpu1 are on
to its index. E.g. ``[0, 0, 1]`` indicates that cpu0 and cpu1 are on
cluster 0, while cpu2 is on cluster 1. If this is not specified, this
will be inferred from ``core_names`` if possible (assuming all cores with
the same name are on the same cluster).

2
wlauto/core/execution.py
View File

@@ -72,7 +72,7 @@ REBOOT_DELAY = 3
class RunInfo(object):
"""
Information about the current run, such as it's unique ID, run
Information about the current run, such as its unique ID, run
time, etc.
"""

6
wlauto/core/extension.py
View File

@@ -303,7 +303,7 @@ class Artifact(object):
network filer archiver may choose to archive them).
.. note: The kind parameter is intended to represent the logical function of a particular
artifact, not it's intended means of processing -- this is left entirely up to the
artifact, not its intended means of processing -- this is left entirely up to the
result processors.
"""
@@ -406,7 +406,7 @@ class ExtensionMeta(type):
def _propagate_attributes(mcs, bases, attrs):
"""
For attributes specified by to_propagate, their values will be a union of
that specified for cls and it's bases (cls values overriding those of bases
that specified for cls and its bases (cls values overriding those of bases
in case of conflicts).
"""
@@ -665,7 +665,7 @@ class Module(Extension):
In other words, a Module is roughly equivalent to a kernel module and its primary purpose is to
implement WA "drivers" for various peripherals that may or may not be present in a particular setup.
.. note:: A mudule is itself an Extension and can therefore have it's own modules.
.. note:: A mudule is itself an Extension and can therefore have its own modules.
"""

2
wlauto/core/resource.py
View File

@@ -82,7 +82,7 @@ class ResourceGetter(Extension):
Base class for implementing resolvers. Defines resolver interface. Resolvers are
responsible for discovering resources (such as particular kinds of files) they know
about based on the parameters that are passed to them. Each resolver also has a dict of
attributes that describe it's operation, and may be used to determine which get invoked.
attributes that describe its operation, and may be used to determine which get invoked.
There is no pre-defined set of attributes and resolvers may define their own.
Class attributes: