This patch series tried to fix trivial spelling fixes.
Bhaskar Chowdhury (23):
atomctl.rst: A typo fix
w1: ds2482.rst: A typo fix
w1-netlink.rst: A typo fix
w1-generic.rst: A typo fix
vm: unevictable-lru.rst: Fix a typo
vm: hwpoison.rst: A typo fix
vm: hwpoison.rst: A typo fix
virt: kvm: vm.rst: Fix a typo
virt: kvm: /mmu.rst: Fix a typo
virt: kvm: halt-polling.rst: Fixed a typo
virt: user_mode_linux_howto_v2.rst: Few typo fixes
v4l: hist-v4l2.rst: Fix a typo
trace: hwlat_detector.rst: Fix a typo
trace: ftrace-uses.rst: Fix a typo
trace: events.rst: Fix a typo
sparc: oradax/oracle-dax.rst: Fix a typo
sparc: dax-hv-api.txt: Fix quite a few spellos
security: core.rst: Fixed a spello
scsi: ChangeLog.ncr53c8xx: Quite a few spello fixes
scheduler: sched-bwc.rst: Fix a typo
scheduler: sched-nice-design.rst: Fix a typo
riscv: pmu.rst : A spello fix
openrisc: openrisc_port.rst: Fix a typo
Documentation/openrisc/openrisc_port.rst | 2 +-
Documentation/riscv/pmu.rst | 2 +-
Documentation/scheduler/sched-bwc.rst | 2 +-
Documentation/scheduler/sched-nice-design.rst | 2 +-
Documentation/scsi/ChangeLog.ncr53c8xx | 260 +++++++++---------
Documentation/security/keys/core.rst | 2 +-
Documentation/sparc/oradax/dax-hv-api.txt | 18 +-
Documentation/sparc/oradax/oracle-dax.rst | 2 +-
Documentation/trace/events.rst | 2 +-
Documentation/trace/ftrace-uses.rst | 2 +-
Documentation/trace/hwlat_detector.rst | 2 +-
.../userspace-api/media/v4l/hist-v4l2.rst | 2 +-
Documentation/virt/kvm/devices/vm.rst | 2 +-
Documentation/virt/kvm/halt-polling.rst | 2 +-
Documentation/virt/kvm/mmu.rst | 2 +-
.../virt/uml/user_mode_linux_howto_v2.rst | 10 +-
Documentation/vm/hwpoison.rst | 4 +-
Documentation/vm/unevictable-lru.rst | 2 +-
Documentation/w1/masters/ds2482.rst | 2 +-
Documentation/w1/w1-generic.rst | 2 +-
Documentation/w1/w1-netlink.rst | 2 +-
Documentation/xtensa/atomctl.rst | 2 +-
22 files changed, 164 insertions(+), 164 deletions(-)
--
2.26.3
s/controlers/controllers/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/xtensa/atomctl.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/xtensa/atomctl.rst b/Documentation/xtensa/atomctl.rst
index 1ecbd0ba9a2e..a0efab2abe8f 100644
--- a/Documentation/xtensa/atomctl.rst
+++ b/Documentation/xtensa/atomctl.rst
@@ -23,7 +23,7 @@ doing a Cached (WB) transaction and use the Memory RCW for un-cached
operations.
For systems without an coherent cache controller, non-MX, we always
-use the memory controllers RCW, thought non-MX controlers likely
+use the memory controllers RCW, thought non-MX controllers likely
support the Internal Operation.
CUSTOMER-WARNING:
--
2.26.3
s/busses/buses/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/w1/masters/ds2482.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/w1/masters/ds2482.rst b/Documentation/w1/masters/ds2482.rst
index 17ebe8f660cd..5862024e4b15 100644
--- a/Documentation/w1/masters/ds2482.rst
+++ b/Documentation/w1/masters/ds2482.rst
@@ -22,7 +22,7 @@ Description
-----------
The Maxim/Dallas Semiconductor DS2482 is a I2C device that provides
-one (DS2482-100) or eight (DS2482-800) 1-wire busses.
+one (DS2482-100) or eight (DS2482-800) 1-wire buses.
General Remarks
--
2.26.3
s/expection/exception/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/vm/hwpoison.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/vm/hwpoison.rst b/Documentation/vm/hwpoison.rst
index a5c884293dac..727f080073dd 100644
--- a/Documentation/vm/hwpoison.rst
+++ b/Documentation/vm/hwpoison.rst
@@ -50,7 +50,7 @@ of applications. KVM support requires a recent qemu-kvm release.
For the KVM use there was need for a new signal type so that
KVM can inject the machine check into the guest with the proper
address. This in theory allows other applications to handle
-memory failures too. The expection is that near all applications
+memory failures too. The exception is that near all applications
won't do that, but some very specialized ones might.
Failure recovery modes
--
2.26.3
s/mmaped/mapped/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/vm/unevictable-lru.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/vm/unevictable-lru.rst b/Documentation/vm/unevictable-lru.rst
index 0e1490524f53..74e7d5ded114 100644
--- a/Documentation/vm/unevictable-lru.rst
+++ b/Documentation/vm/unevictable-lru.rst
@@ -467,7 +467,7 @@ In addition the mlock()/mlockall() system calls, an application can request
that a region of memory be mlocked supplying the MAP_LOCKED flag to the mmap()
call. There is one important and subtle difference here, though. mmap() + mlock()
will fail if the range cannot be faulted in (e.g. because mm_populate fails)
-and returns with ENOMEM while mmap(MAP_LOCKED) will not fail. The mmaped
+and returns with ENOMEM while mmap(MAP_LOCKED) will not fail. The mapped
area will still have properties of the locked area - aka. pages will not get
swapped out - but major page faults to fault memory in might still happen.
--
2.26.3
s/strucutre/structure/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/w1/w1-netlink.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/w1/w1-netlink.rst b/Documentation/w1/w1-netlink.rst
index aaa13243a5e4..be4f7b82dcb4 100644
--- a/Documentation/w1/w1-netlink.rst
+++ b/Documentation/w1/w1-netlink.rst
@@ -66,7 +66,7 @@ Each connector message can include one or more w1_netlink_msg with
zero or more attached w1_netlink_cmd messages.
For event messages there are no w1_netlink_cmd embedded structures,
-only connector header and w1_netlink_msg strucutre with "len" field
+only connector header and w1_netlink_msg structure with "len" field
being zero and filled type (one of event types) and id:
either 8 bytes of slave unique id in host order,
or master's id, which is assigned to bus master device
--
2.26.3
s/beetwen/between/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/w1/w1-generic.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/w1/w1-generic.rst b/Documentation/w1/w1-generic.rst
index da4e8b4e9b01..229b16b6399b 100644
--- a/Documentation/w1/w1-generic.rst
+++ b/Documentation/w1/w1-generic.rst
@@ -101,7 +101,7 @@ w1_master_search (rw) the number of searches left to do,
w1_master_slave_count (ro) the number of slaves found
w1_master_slaves (ro) the names of the slaves, one per line
w1_master_timeout (ro) the delay in seconds between searches
-w1_master_timeout_us (ro) the delay in microseconds beetwen searches
+w1_master_timeout_us (ro) the delay in microseconds between searches
========================= =====================================================
If you have a w1 bus that never changes (you don't add or remove devices),
--
2.26.3
s/imlemented/implemented/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/virt/kvm/devices/vm.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/kvm/devices/vm.rst b/Documentation/virt/kvm/devices/vm.rst
index 0aa5b1cfd700..3eb1abf505c9 100644
--- a/Documentation/virt/kvm/devices/vm.rst
+++ b/Documentation/virt/kvm/devices/vm.rst
@@ -92,7 +92,7 @@ Allows user space to retrieve or request to change cpu related information for a
KVM does not enforce or limit the cpu model data in any form. Take the information
retrieved by means of KVM_S390_VM_CPU_MACHINE as hint for reasonable configuration
setups. Instruction interceptions triggered by additionally set facility bits that
-are not handled by KVM need to by imlemented in the VM driver code.
+are not handled by KVM need to by implemented in the VM driver code.
:Parameters: address of buffer to store/set the processor related cpu
data of type struct kvm_s390_vm_cpu_processor*.
--
2.26.3
s/focusses/focuses/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/vm/hwpoison.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/vm/hwpoison.rst b/Documentation/vm/hwpoison.rst
index 727f080073dd..7840463a0e9a 100644
--- a/Documentation/vm/hwpoison.rst
+++ b/Documentation/vm/hwpoison.rst
@@ -19,7 +19,7 @@ To quote the overview comment::
hardware as being corrupted usually due to a 2bit ECC memory or cache
failure.
- This focusses on pages detected as corrupted in the background.
+ This focuses on pages detected as corrupted in the background.
When the current CPU tries to consume corruption the currently
running process can just be killed directly instead. This implies
that if the error cannot be handled for some reason it's safe to
--
2.26.3
s/dependant/dependent/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/virt/kvm/halt-polling.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/kvm/halt-polling.rst b/Documentation/virt/kvm/halt-polling.rst
index 4922e4a15f18..c428d319de45 100644
--- a/Documentation/virt/kvm/halt-polling.rst
+++ b/Documentation/virt/kvm/halt-polling.rst
@@ -14,7 +14,7 @@ before giving up the cpu to the scheduler in order to let something else run.
Polling provides a latency advantage in cases where the guest can be run again
very quickly by at least saving us a trip through the scheduler, normally on
the order of a few micro-seconds, although performance benefits are workload
-dependant. In the event that no wakeup source arrives during the polling
+dependent. In the event that no wakeup source arrives during the polling
interval or some other task on the runqueue is runnable the scheduler is
invoked. Thus halt polling is especially useful on workloads with very short
wakeup periods where the time spent halt polling is minimised and the time
--
2.26.3
s/unsychronized/unsynchronized/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/virt/kvm/mmu.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/kvm/mmu.rst b/Documentation/virt/kvm/mmu.rst
index 5bfe28b0728e..e6c525280813 100644
--- a/Documentation/virt/kvm/mmu.rst
+++ b/Documentation/virt/kvm/mmu.rst
@@ -244,7 +244,7 @@ Shadow pages contain the following information:
unsynchronized children).
unsync_child_bitmap:
A bitmap indicating which sptes in spt point (directly or indirectly) at
- pages that may be unsynchronized. Used to quickly locate all unsychronized
+ pages that may be unsynchronized. Used to quickly locate all unsynchronized
pages reachable from a given page.
clear_spte_count:
Only present on 32-bit hosts, where a 64-bit spte cannot be written
--
2.26.3
s/occuring/occurring/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/trace/hwlat_detector.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/trace/hwlat_detector.rst b/Documentation/trace/hwlat_detector.rst
index 5739349649c8..f7811e2ddf34 100644
--- a/Documentation/trace/hwlat_detector.rst
+++ b/Documentation/trace/hwlat_detector.rst
@@ -14,7 +14,7 @@ originally written for use by the "RT" patch since the Real Time
kernel is highly latency sensitive.
SMIs are not serviced by the Linux kernel, which means that it does not
-even know that they are occuring. SMIs are instead set up by BIOS code
+even know that they are occurring. SMIs are instead set up by BIOS code
and are serviced by BIOS code, usually for "critical" events such as
management of thermal sensors and fans. Sometimes though, SMIs are used for
other tasks and those tasks can spend an inordinate amount of time in the
--
2.26.3
s/directon/director/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/userspace-api/media/v4l/hist-v4l2.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/userspace-api/media/v4l/hist-v4l2.rst b/Documentation/userspace-api/media/v4l/hist-v4l2.rst
index 28a2750d5c8c..7061496126ad 100644
--- a/Documentation/userspace-api/media/v4l/hist-v4l2.rst
+++ b/Documentation/userspace-api/media/v4l/hist-v4l2.rst
@@ -47,7 +47,7 @@ Codec API was released.
1998-11-08: Many minor changes. Most symbols have been renamed. Some
material changes to struct v4l2_capability.
-1998-11-12: The read/write directon of some ioctls was misdefined.
+1998-11-12: The read/write director of some ioctls was misdefined.
1998-11-14: ``V4L2_PIX_FMT_RGB24`` changed to ``V4L2_PIX_FMT_BGR24``,
and ``V4L2_PIX_FMT_RGB32`` changed to ``V4L2_PIX_FMT_BGR32``. Audio
--
2.26.3
s/absense/absence/
s/sripts/scripts/
s/resultion/resolution/
s/desireable/desirable/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/virt/uml/user_mode_linux_howto_v2.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/virt/uml/user_mode_linux_howto_v2.rst b/Documentation/virt/uml/user_mode_linux_howto_v2.rst
index 312e431695d9..0e1371c3e235 100644
--- a/Documentation/virt/uml/user_mode_linux_howto_v2.rst
+++ b/Documentation/virt/uml/user_mode_linux_howto_v2.rst
@@ -317,7 +317,7 @@ Shared Options
* ``v6=[0,1]`` to specify if a v6 connection is desired for all
transports which operate over IP. Additionally, for transports that
have some differences in the way they operate over v4 and v6 (for example
- EoL2TPv3), sets the correct mode of operation. In the absense of this
+ EoL2TPv3), sets the correct mode of operation. In the absence of this
option, the socket type is determined based on what do the src and dst
arguments resolve/parse to.
@@ -726,7 +726,7 @@ kernel. When you boot UML, you'll see a line like::
mconsole initialized on /home/jdike/.uml/umlNJ32yL/mconsole
-If you specify a unique machine id one the UML command line, i.e.
+If you specify a unique machine id one the UML command line, i.e.
``umid=debian``, you'll see this::
mconsole initialized on /home/jdike/.uml/debian/mconsole
@@ -1073,7 +1073,7 @@ If you have something to contribute such as a patch, a bugfix, a
new feature, please send it to ``[email protected]``
Please follow all standard Linux patch guidelines such as cc-ing
-relevant maintainers and run ``./sripts/checkpatch.pl`` on your patch.
+relevant maintainers and run ``./scripts/checkpatch.pl`` on your patch.
For more details see ``Documentation/process/submitting-patches.rst``
Note - the list does not accept HTML or attachments, all emails must
@@ -1131,7 +1131,7 @@ This is a typical picture from a mostly idle UML instance
* The sequence of ptrace calls is part of MMU emulation and runnin the
UML userspace
* ``timer_settime`` is part of the UML high res timer subsystem mapping
- timer requests from inside UML onto the host high resultion timers.
+ timer requests from inside UML onto the host high resolution timers.
* ``clock_nanosleep`` is UML going into idle (similar to the way a PC
will execute an ACPI idle).
@@ -1195,7 +1195,7 @@ between a driver and the host at the UML command line is OK
security-wise. Allowing it as a loadable module parameter
isn't.
-If such functionality is desireable for a particular application
+If such functionality is desirable for a particular application
(e.g. loading BPF "firmware" for raw socket network transports),
it should be off by default and should be explicitly turned on
as a command line parameter at startup.
--
2.26.3
s/specfied/specified/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/trace/events.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/trace/events.rst b/Documentation/trace/events.rst
index 8ddb9b09451c..80052adc592d 100644
--- a/Documentation/trace/events.rst
+++ b/Documentation/trace/events.rst
@@ -884,7 +884,7 @@ functions can be used.
To create a kprobe event, an empty or partially empty kprobe event
should first be created using kprobe_event_gen_cmd_start(). The name
-of the event and the probe location should be specfied along with one
+of the event and the probe location should be specified along with one
or args each representing a probe field should be supplied to this
function. Before calling kprobe_event_gen_cmd_start(), the user
should create and initialize a dynevent_cmd object using
--
2.26.3
s/discontiguities/discontinuities/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/sparc/oradax/oracle-dax.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/sparc/oradax/oracle-dax.rst b/Documentation/sparc/oradax/oracle-dax.rst
index d1e14d572918..54ccb35ed51d 100644
--- a/Documentation/sparc/oradax/oracle-dax.rst
+++ b/Documentation/sparc/oradax/oracle-dax.rst
@@ -197,7 +197,7 @@ Memory Constraints
==================
The DAX hardware operates only on physical addresses. Therefore, it is
-not aware of virtual memory mappings and the discontiguities that may
+not aware of virtual memory mappings and the discontinuities that may
exist in the physical memory that a virtual buffer maps to. There is
no I/O TLB or any scatter/gather mechanism. All buffers, whether input
or output, must reside in a physically contiguous region of memory.
--
2.26.3
s/indicies/indices/
s/retricted/restricted/
s/indentifier/identifier/ ....two different places.
s/proccessed/processed/ ....three different places.
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/sparc/oradax/dax-hv-api.txt | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/Documentation/sparc/oradax/dax-hv-api.txt b/Documentation/sparc/oradax/dax-hv-api.txt
index 73e8d506cf64..300fbb58ad04 100644
--- a/Documentation/sparc/oradax/dax-hv-api.txt
+++ b/Documentation/sparc/oradax/dax-hv-api.txt
@@ -742,7 +742,7 @@ Offset Size Field Description
code in the CCB header.
There are two supported formats for the output stream: the bit vector and index array formats (codes 0x8,
- 0xD, and 0xE). The index array format is an array of indicies of bits which would have been set if the
+ 0xD, and 0xE). The index array format is an array of indices of bits which would have been set if the
output format was a bit array.
The return value of the CCB completion area contains the number of bits set in the output bit vector,
@@ -1254,7 +1254,7 @@ EUNAVAILABLE The requested CCB operation could not be performed at this time.
submitted CCB, or may apply to a larger scope. The status should not be
interpreted as permanent, and the guest should attempt to submit CCBs in
the future which had previously been unable to be performed. The status
- data provides additional information about scope of the retricted availability
+ data provides additional information about scope of the restricted availability
as follows:
Value Description
0 Processing for the exact CCB instance submitted was unavailable,
@@ -1330,20 +1330,20 @@ EUNAVAILABLE The requested CCB operation could not be performed at this time.
of other CCBs ahead of the requested CCB, to provide a relative estimate of when the CCB may execute.
The dax return value is only valid when the state is ENQUEUED. The value returned is the DAX unit
- instance indentifier for the DAX unit processing the queue where the requested CCB is located. The value
+ instance identifier for the DAX unit processing the queue where the requested CCB is located. The value
matches the value that would have been, or was, returned by ccb_submit using the queue info flag.
The queue return value is only valid when the state is ENQUEUED. The value returned is the DAX
- queue instance indentifier for the DAX unit processing the queue where the requested CCB is located. The
+ queue instance identifier for the DAX unit processing the queue where the requested CCB is located. The
value matches the value that would have been, or was, returned by ccb_submit using the queue info flag.
36.3.2.1. Errors
- EOK The request was proccessed and the CCB state is valid.
+ EOK The request was processed and the CCB state is valid.
EBADALIGN address is not on a 64-byte aligned.
ENORADDR The real address provided for address is not valid.
EINVAL The CCB completion area contents are not valid.
- EWOULDBLOCK Internal resource contraints prevented the CCB state from being queried at this
+ EWOULDBLOCK Internal resource constraints prevented the CCB state from being queried at this
time. The guest should retry the request.
ENOACCESS The guest does not have permission to access the coprocessor virtual device
functionality.
@@ -1401,11 +1401,11 @@ EUNAVAILABLE The requested CCB operation could not be performed at this time.
36.3.3.2. Errors
- EOK The request was proccessed and the result is valid.
+ EOK The request was processed and the result is valid.
EBADALIGN address is not on a 64-byte aligned.
ENORADDR The real address provided for address is not valid.
EINVAL The CCB completion area contents are not valid.
- EWOULDBLOCK Internal resource contraints prevented the CCB from being killed at this time.
+ EWOULDBLOCK Internal resource constraints prevented the CCB from being killed at this time.
The guest should retry the request.
ENOACCESS The guest does not have permission to access the coprocessor virtual device
functionality.
@@ -1423,7 +1423,7 @@ EUNAVAILABLE The requested CCB operation could not be performed at this time.
36.3.4.1. Errors
- EOK The request was proccessed and the number of enabled/disabled DAX units
+ EOK The request was processed and the number of enabled/disabled DAX units
are valid.
--
2.26.3
s/implemenation/implementation/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/security/keys/core.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/security/keys/core.rst b/Documentation/security/keys/core.rst
index b3ed5c581034..d66ad592c6cc 100644
--- a/Documentation/security/keys/core.rst
+++ b/Documentation/security/keys/core.rst
@@ -869,7 +869,7 @@ The keyctl syscall functions are:
- ``char *hashname`` specifies the NUL terminated string identifying
the hash used from the kernel crypto API and applied for the KDF
- operation. The KDF implemenation complies with SP800-56A as well
+ operation. The KDF implementation complies with SP800-56A as well
as with SP800-108 (the counter KDF).
- ``char *otherinfo`` specifies the OtherInfo data as documented in
--
2.26.3
Few trivial spelling fixes.
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Few lines have done self modification, means they eliminate and added
themselves. I have no clue why that happen.
Documentation/scsi/ChangeLog.ncr53c8xx | 260 ++++++++++++-------------
1 file changed, 130 insertions(+), 130 deletions(-)
diff --git a/Documentation/scsi/ChangeLog.ncr53c8xx b/Documentation/scsi/ChangeLog.ncr53c8xx
index 9288e3d8974a..0dacfeef22a5 100644
--- a/Documentation/scsi/ChangeLog.ncr53c8xx
+++ b/Documentation/scsi/ChangeLog.ncr53c8xx
@@ -9,8 +9,8 @@ Mon Feb 12 22:30 2001 Gerard Roudier ([email protected])
- Call pci_enable_device() as AC wants this to be done.
- Get both the BAR cookies actual and PCI BAR values.
(see Changelog.sym53c8xx rev. 1.7.3 for details)
- - Merge changes for linux-2.4 that declare the host template
- in the driver object also when the driver is statically
+ - Merge changes for linux-2.4 that declare the host template
+ in the driver object also when the driver is statically
linked with the kernel.
Sun Sep 24 21:30 2000 Gerard Roudier ([email protected])
@@ -25,34 +25,34 @@ Wed Jul 26 23:30 2000 Gerard Roudier ([email protected])
Sun Jul 09 16:30 2000 Gerard Roudier ([email protected])
* version ncr53c8xx-3.4.0
- Remove the PROFILE C and SCRIPTS code.
- This facility was not this useful and thus was not longer
+ This facility was not this useful and thus was not longer
desirable given the increasing complexity of the driver code.
- Merges from FreeBSD sym-1.6.2 driver:
- * Clarify memory barriers needed by the driver for architectures
+ * Clarify memory barriers needed by the driver for architectures
that implement a weak memory ordering.
- General cleanup:
- Move definitions for barriers and IO/MMIO operations to the
- sym53c8xx_defs.h header files. They are now shared by the
+ Move definitions for barriers and IO/MMIO operations to the
+ sym53c8xx_defs.h header files. They are now shared by the
both drivers.
Use SCSI_NCR_IOMAPPED instead of NCR_IOMAPPED.
Thu May 11 12:30 2000 Pam Delaney ([email protected])
* revision 3.3b
-
+
Mon Apr 24 12:00 2000 Gerard Roudier ([email protected])
* revision 3.2i
- Return value 1 (instead of 0) from the driver setup routine.
- - Let the driver also attach controllers that have been set to
+ - Let the driver also attach controllers that have been set to
OFF in the NVRAM as it did prior to revision 3.2g.
Sat Apr 1 12:00 2000 Gerard Roudier ([email protected])
* revision 3.2h
- Fix a compilation problem on Alpha introduced in version 3.2g.
(`port' changed to `base_io').
- - Move from `sym' to this driver a tiny change for __sparc__ that
+ - Move from `sym' to this driver a tiny change for __sparc__ that
applies to cache line size (? Probably from David S Miller).
- - Make sure no data transfer will happen for Scsi_Cmnd requests
- that supply SCSI_DATA_NONE direction (this avoids some BUG()
+ - Make sure no data transfer will happen for Scsi_Cmnd requests
+ that supply SCSI_DATA_NONE direction (this avoids some BUG()
statement in the PCI code when a data buffer is also supplied).
Thu Mar 16 9:30 2000 Pam Delaney ([email protected])
@@ -62,10 +62,10 @@ Thu Mar 16 9:30 2000 Pam Delaney ([email protected])
Mon March 6 23:15 2000 Gerard Roudier ([email protected])
* revision 3.2g
- - Add the file sym53c8xx_comm.h that collects code that should
- be shared by sym53c8xx and ncr53c8xx drivers. For now, it is
- a header file that is only included by the ncr53c8xx driver,
- but things will be cleaned up later. This code addresses
+ - Add the file sym53c8xx_comm.h that collects code that should
+ be shared by sym53c8xx and ncr53c8xx drivers. For now, it is
+ a header file that is only included by the ncr53c8xx driver,
+ but things will be cleaned up later. This code addresses
notably:
* Chip detection and PCI related initialisations
* NVRAM detection and reading
@@ -74,7 +74,7 @@ Mon March 6 23:15 2000 Gerard Roudier ([email protected])
* And some other ...
- Add support for the new dynamic dma mapping kernel interface.
Requires Linux-2.3.47 (tested with pre-2.3.47-6).
- - Get data transfer direction from the scsi command structure
+ - Get data transfer direction from the scsi command structure
(Scsi_Cmnd) when this information is available.
Mon March 6 23:15 2000 Gerard Roudier ([email protected])
@@ -96,12 +96,12 @@ Mon March 6 23:15 2000 Gerard Roudier ([email protected])
Fri Jan 14 14:00 2000 Pam Delaney ([email protected])
* revision pre-3.3b-1
- - Merge parallel driver series 3.31 and 3.2e
+ - Merge parallel driver series 3.31 and 3.2e
Tue Jan 11 14:00 2000 Pam Delaney ([email protected])
* revision 3.31
- Added support for mounting disks on wide-narrow-wide
- scsi configurations.
+ scsi configurations.
- Built off of version 3.30
Mon Jan 10 13:30 2000 Pam Delaney ([email protected])
@@ -119,24 +119,24 @@ Sat Jan 8 22:00 2000 Gerard Roudier ([email protected])
Mon Dec 6 22:00 1999 Gerard Roudier ([email protected])
* revision 3.2d
- - Change messages written by the driver at initialisation and
+ - Change messages written by the driver at initialisation and
through the /proc FS (rather cosmetic changes that consist in
printing out the PCI bus number and device/function).
- - Get rid of the old PCI bios interface, but preserve kernel 2.0
+ - Get rid of the old PCI bios interface, but preserve kernel 2.0
compatibility from a simple wrapper.
- - Remove the compilation condition about having to acquire the
+ - Remove the compilation condition about having to acquire the
io_request_lock since it seems to be a definite feature now.:)
- proc_dir structure no longer needed for kernel >= 2.3.27.
- - Change the driver detection code by the sym53c8xx one, modulo
- some minor changes. The driver can now attach any number of
- controllers (>40) and does no longer hoger stack space at
+ - Change the driver detection code by the sym53c8xx one, modulo
+ some minor changes. The driver can now attach any number of
+ controllers (>40) and does no longer hoger stack space at
initialisation.
- - Definitely disable overlapped PCI arbitration for all dual
- function chips, since I cannot make sure for what chip revisions
+ - Definitely disable overlapped PCI arbitration for all dual
+ function chips, since I cannot make sure for what chip revisions
it is actually safe.
- Add support for the SYM53C1510D.
- Update the poor Tekram sync factor table.
- - Remove the compilation condition about having to acquire the
+ - Remove the compilation condition about having to acquire the
io_request_lock since it seems to be a definite feature now.:)
- proc_dir structure no longer needed for kernel >= 2.3.27.
@@ -145,25 +145,25 @@ Sat Sep 11 18:00 1999 Gerard Roudier ([email protected])
- Handle correctly (hopefully) jiffies wrap-around.
- Restore the entry used to detect 875 until revision 0xff.
(I removed it inadvertently, it seems :) )
- - Replace __initfunc() which is deprecated stuff by __init which
+ - Replace __initfunc() which is deprecated stuff by __init which
is not yet so. ;-)
- Add support of some 'resource handling' for linux-2.3.13.
- Basically the BARs have been changed to something more complex
+ Basically the BARs have been changed to something more complex
in the pci_dev structure.
- Remove some deprecated code.
Sat May 10 11:00 1999 Gerard Roudier ([email protected])
* revision pre-3.2b-1
- Support for the 53C895A by Pamela Delaney <[email protected]>
- The 53C895A contains all of the features of the 896 but has only
- one channel and has a 32 bit PCI bus. It does 64 bit PCI addressing
+ The 53C895A contains all of the features of the 896 but has only
+ one channel and has a 32 bit PCI bus. It does 64 bit PCI addressing
using dual cycle PCI data transfers.
- Miscellaneous minor fixes.
- Some additions to the README.ncr53c8xx file.
Sun Apr 11 10:00 1999 Gerard Roudier ([email protected])
* revision 3.2a
- - Add 'hostid:#id' boot option. This option allows to change the
+ - Add 'hostid:#id' boot option. This option allows to change the
default SCSI id the driver uses for controllers.
- Remove nvram layouts and driver set-up structures from the C source,
and use the one defined in sym53c8xx_defs.h file.
@@ -172,20 +172,20 @@ Sun Apr 11 10:00 1999 Gerard Roudier ([email protected])
Thu Mar 11 23:00 1999 Gerard Roudier ([email protected])
* revision 3.2 (8xx-896 driver bundle)
- - Only define the host template in ncr53c8xx.h and include the
+ - Only define the host template in ncr53c8xx.h and include the
sym53c8xx_defs.h file.
- - Declare static all symbols that do not need to be visible from
+ - Declare static all symbols that do not need to be visible from
outside the driver code.
- - Add 'excl' boot command option that allows to pass to the driver
+ - Add 'excl' boot command option that allows to pass to the driver
io address of devices not to attach.
- - Add info() function called from the host template to print
+ - Add info() function called from the host template to print
driver/host information.
- Minor documentation additions.
Sat Mar 6 11:00 1999 Gerard Roudier ([email protected])
* revision 3.1h
- - Fix some oooold bug that hangs the bus if a device rejects a
- negotiation. Btw, the corresponding stuff also needed some cleanup
+ - Fix some oooold bug that hangs the bus if a device rejects a
+ negotiation. Btw, the corresponding stuff also needed some cleanup
and thus the change is a bit larger than it could have been.
- Still some typo that made compilation fail for 64 bit (trivial fix).
@@ -193,14 +193,14 @@ Sun Feb 14:00 1999 Gerard Roudier ([email protected])
* revision 3.1g
- Deal correctly with 64 bit PCI address registers on Linux 2.2.
Pointed out by Leonard Zubkoff.
- - Allow to tune request_irq() flags from the boot command line using
+ - Allow to tune request_irq() flags from the boot command line using
ncr53c8xx=irqm:??, as follows:
a) If bit 0x10 is set in irqm, IRQF_SHARED flag is not used.
b) If bit 0x20 is set in irqm, IRQF_DISABLED flag is not used.
By default the driver uses both IRQF_SHARED and IRQF_DISABLED.
- Option 'ncr53c8xx=irqm:0x20' may be used when an IRQ is shared by
+ Option 'ncr53c8xx=irqm:0x20' may be used when an IRQ is shared by
a 53C8XX adapter and a network board.
- - Tiny misspelling fixed (ABORT instead of ABRT). Was fortunately
+ - Tiny misspelling fixed (ABORT instead of ABRT). Was fortunately
harmless.
- Negotiate SYNC data transfers with CCS devices.
@@ -214,12 +214,12 @@ Sat Jan 16 17:30 1999 Gerard Roudier ([email protected])
Sun Dec 13 18:00 1998 Gerard Roudier ([email protected])
* revision 3.1e
- Same work-around as for the 53c876 rev <= 0x15 for 53c896 rev 1:
- Disable overlapped arbitration. This will not make difference
+ Disable overlapped arbitration. This will not make difference
since the chip has on-chip RAM.
Thu Nov 26 22:00 1998 Gerard Roudier ([email protected])
* revision 3.1d
- - The SISL RAID change requires now remap_pci_mem() stuff to be
+ - The SISL RAID change requires now remap_pci_mem() stuff to be
compiled for __i386__ when normal IOs are used.
- Minor spelling fixes in doc files.
@@ -228,9 +228,9 @@ Sat Nov 21 18:00 1998 Gerard Roudier ([email protected])
- Ignore chips that are driven by SISL RAID (DAC 960).
Change sent by Leonard Zubkoff and slightly reworked.
- Still a buglet in the tags initial settings that needed to be fixed.
- It was not possible to disable TGQ at system startup for devices
- that claim TGQ support. The driver used at least 2 for the queue
- depth but did'nt keep track of user settings for tags depth lower
+ It was not possible to disable TGQ at system startup for devices
+ that claim TGQ support. The driver used at least 2 for the queue
+ depth but didn't keep track of user settings for tags depth lower
than 2.
Wed Nov 11 10:00 1998 Gerard Roudier ([email protected])
@@ -244,54 +244,54 @@ Wed Oct 21 21:00 1998 Gerard Roudier ([email protected])
- Changes from Eddie Dost for Sparc and Alpha:
ioremap/iounmap support for Sparc.
pcivtophys changed to bus_dvma_to_phys.
- - Add the 53c876 description to the chip table. This is only useful
+ - Add the 53c876 description to the chip table. This is only useful
for printing the right name of the controller.
- DEL-441 Item 2 work-around for the 53c876 rev <= 5 (0x15).
- Add additional checking of INQUIRY data:
- Check INQUIRY data received length is at least 7. Byte 7 of
- inquiry data contains device features bits and the driver might
+ Check INQUIRY data received length is at least 7. Byte 7 of
+ inquiry data contains device features bits and the driver might
be confused by garbage. Also check peripheral qualifier.
- Cleanup of the SCSI tasks management:
- Remove the special case for 32 tags. Now the driver only uses the
+ Remove the special case for 32 tags. Now the driver only uses the
scheme that allows up to 64 tags per LUN.
Merge some code from the 896 driver.
- Use a 1,3,5,...MAXTAGS*2+1 tag numbering. Previous driver could
- use any tag number from 1 to 253 and some non conformant devices
+ Use a 1,3,5,...MAXTAGS*2+1 tag numbering. Previous driver could
+ use any tag number from 1 to 253 and some non conformant devices
might have problems with large tag numbers.
- - 'no_sync' changed to 'no_disc' in the README file. This is an old
- and trivial mistake that seems to demonstrate the README file is
+ - 'no_sync' changed to 'no_disc' in the README file. This is an old
+ and trivial mistake that seems to demonstrate the README file is
not often read. :)
Sun Oct 4 14:00 1998 Gerard Roudier ([email protected])
* revision 3.0i
- - Cosmetic changes for sparc (but not for the driver) that needs
+ - Cosmetic changes for sparc (but not for the driver) that needs
__irq_itoa() to be used for printed IRQ value to be understandable.
- - Some problems with the driver that didn't occur using driver 2.5f
- were due to a SCSI selection problem triggered by a clearly
- documented feature that in fact seems not to work: (53C8XX chips
- are claimed by the manuals to be able to execute SCSI scripts just
- after abitration while the SCSI core is performing SCSI selection).
+ - Some problems with the driver that didn't occur using driver 2.5f
+ were due to a SCSI selection problem triggered by a clearly
+ documented feature that in fact seems not to work: (53C8XX chips
+ are claimed by the manuals to be able to execute SCSI scripts just
+ after arbitration while the SCSI core is performing SCSI selection).
This optimization is broken and has been removed.
- - Some broken scsi devices are confused when a negotiation is started
- on a LUN that does not correspond to a real device. According to
- SCSI specs, this is a device firmware bug. This has been worked
- around by only starting negotiation if the LUN has previously be
+ - Some broken scsi devices are confused when a negotiation is started
+ on a LUN that does not correspond to a real device. According to
+ SCSI specs, this is a device firmware bug. This has been worked
+ around by only starting negotiation if the LUN has previously be
used for at least 1 successful SCSI command.
- - The 'last message sent' printed out on M_REJECT message reception
- was read from the SFBR i/o register after the previous message had
- been sent.
- This was not correct and affects all previous driver versions and
- the original FreeBSD one as well. The SCSI scripts has been fixed
+ - The 'last message sent' printed out on M_REJECT message reception
+ was read from the SFBR i/o register after the previous message had
+ been sent.
+ This was not correct and affects all previous driver versions and
+ the original FreeBSD one as well. The SCSI scripts has been fixed
so that it now provides the right information to the C code.
Sat Jul 18 13:00 1998 Gerard Roudier ([email protected])
* revision 3.0g
- Preliminary fixes for Big Endian (sent by Eddie C. Dost).
Big Endian architectures should work again with the driver.
- Eddie's patch has been partially applied since current 2.1.109
+ Eddie's patch has been partially applied since current 2.1.109
does not have all the Sparc changes of the vger tree.
- Use of BITS_PER_LONG instead of (~0UL == 0xffffffffUL) has fixed
- the problem observed when the driver was compiled using EGCS or
+ the problem observed when the driver was compiled using EGCS or
PGCC.
Mon Jul 13 20:00 1998 Gerard Roudier ([email protected])
@@ -299,19 +299,19 @@ Mon Jul 13 20:00 1998 Gerard Roudier ([email protected])
- Some spelling fixes.
- linux/config.h misplaced in ncr53c8xx.h
- MODULE_PARM stuff added for linux 2.1.
- - check INQUIRY response data format is exactly 2.
- - use BITS_PER_LONG if defined.
+ - check INQUIRY response data format is exactly 2.
+ - use BITS_PER_LONG if defined.
Sun Jun 28 12:00 1998 Gerard Roudier ([email protected])
* revision 3.0e
- - Some cleanup, spelling fixes, version checks, documentations
+ - Some cleanup, spelling fixes, version checks, documentations
changes, etc ...
Sat Jun 20 20:00 1998 Gerard Roudier ([email protected])
* revision 3.0c
- - Add a boot setup option that allows to set up device queue depths
- at boot-up. This option is very useful since Linux does not
- allow to change scsi device queue depth once the system has been
+ - Add a boot setup option that allows to set up device queue depths
+ at boot-up. This option is very useful since Linux does not
+ allow to change scsi device queue depth once the system has been
booted up.
Sun Jun 15 23:00 1998 Gerard Roudier ([email protected])
@@ -319,25 +319,25 @@ Sun Jun 15 23:00 1998 Gerard Roudier ([email protected])
- Support for up to 64 TAGS per LUN.
- Rewrite the TARGET vs LUN capabilities management.
CmdQueue is now handled as a LUN capability as it shall be.
- This also fixes a bug triggered when disabling tagged command
+ This also fixes a bug triggered when disabling tagged command
queuing for a device that had this feature enabled.
- - Remove the ncr_opennings() stuff that was useless under Linux
+ - Remove the ncr_opennings() stuff that was useless under Linux
and hard to understand to me.
- - Add "setverbose" procfs driver command. It allows to tune
- verbose level after boot-up. Setting this level to zero, for
+ - Add "setverbose" procfs driver command. It allows to tune
+ verbose level after boot-up. Setting this level to zero, for
example avoid flooding the syslog file.
- Add KERN_XXX to some printk's.
Tue Jun 10 23:00 1998 Gerard Roudier ([email protected])
* revision 3.0
- Linux config changes for 2.0.34:
- Remove NVRAM detection config option. This option is now enabled
+ Remove NVRAM detection config option. This option is now enabled
by default but can be disabled by editing the driver header file.
Add a PROFILE config option.
- Update Configure.help
- - Add calls to new function mdelay() for milli-seconds delay if
+ - Add calls to new function mdelay() for milli-seconds delay if
kernel version >= 2.1.105.
- - Replace all printf(s) by printk(s). After all, the ncr53c8xx is
+ - Replace all printf(s) by printk(s). After all, the ncr53c8xx is
a driver for Linux.
- Perform auto-sense on COMMAND TERMINATED. Not sure it is useful.
- Some other minor changes.
@@ -347,40 +347,40 @@ Tue Jun 4 23:00 1998 Gerard Roudier ([email protected])
- Code cleanup and simplification:
Remove kernel 1.2.X and 1.3.X support.
Remove the _old_ target capabilities table.
- Remove the error recovery code that have'nt been really useful.
- Use a single alignment boundary (CACHE_LINE_SIZE) for data
+ Remove the error recovery code that haven't been really useful.
+ Use a single alignment boundary (CACHE_LINE_SIZE) for data
structures.
- Several aggressive SCRIPTS optimizations and changes:
Reselect SCRIPTS code rewritten.
Support for selection/reselection without ATN.
And some others.
- - Miscallaneous changes in the C code:
+ - Miscellaneous changes in the C code:
Count actual number of CCB queued to the controller (future use).
Lots of other minor changes.
Wed May 13 20:00 1998 Gerard Roudier ([email protected])
* revision 2.6m
- - Problem of missed SCSI bus reset with the 53C895 fixed by
- Richard Waltham. The 53C895 needs about 650 us for the bus
- mode to settle. Delays used while resetting the controller
+ - Problem of missed SCSI bus reset with the 53C895 fixed by
+ Richard Waltham. The 53C895 needs about 650 us for the bus
+ mode to settle. Delays used while resetting the controller
and the bus have been adjusted. Thanks Richard!
- Some simplification for 64 bit arch done ccb address testing.
- Add a check of the MSG_OUT phase after Selection with ATN.
- - The new tagged queue stuff seems ok, so some informationnal
- message have been conditionned by verbose >= 3.
- - Donnot reset if a SBMC interrupt reports the same bus mode.
- - Print out the whole driver set-up. Some options were missing and
+ - The new tagged queue stuff seems ok, so some informational
+ message have been conditioned by verbose >= 3.
+ - Don not reset if a SBMC interrupt reports the same bus mode.
+ - Print out the whole driver set-up. Some options were missing and
the print statement was misplaced for modules.
- - Ignore a SCSI parity interrupt if the chip is not connected to
+ - Ignore a SCSI parity interrupt if the chip is not connected to
the SCSI bus.
Sat May 1 16:00 1998 Gerard Roudier ([email protected])
* revision 2.6l
- - Add CCB done queue support for Alpha and perhaps some other
+ - Add CCB done queue support for Alpha and perhaps some other
architectures.
- - Add some barriers to enforce memory ordering for x86 and
+ - Add some barriers to enforce memory ordering for x86 and
Alpha architectures.
- - Fix something that looks like an old bug in the nego SIR
+ - Fix something that looks like an old bug in the nego SIR
interrupt code in case of negotiation failure.
Sat Apr 25 21:00 1998 Gerard Roudier ([email protected])
@@ -388,11 +388,11 @@ Sat Apr 25 21:00 1998 Gerard Roudier ([email protected])
- Remove all accesses to the on-chip RAM from the C code:
Use SCRIPTS to load the on-chip RAM.
Use SCRIPTS to repair the start queue on selection timeout.
- Use the copy of script in main memory to calculate the chip
+ Use the copy of script in main memory to calculate the chip
context on phase mismatch.
- - The above allows now to use the on-chip RAM without requiring
- to get access to the on-chip RAM from the C code. This makes
- on-chip RAM useable for linux-1.2.13 and for Linux-Alpha for
+ - The above allows now to use the on-chip RAM without requiring
+ to get access to the on-chip RAM from the C code. This makes
+ on-chip RAM useable for linux-1.2.13 and for Linux-Alpha for
instance.
- Some simplifications and cleanups in the SCRIPTS and C code.
- Buglet fixed in parity error recovery SCRIPTS (never tested).
@@ -402,28 +402,28 @@ Wed Apr 15 21:00 1998 Gerard Roudier ([email protected])
* revision 2.6j
- Incorporate changes from linux-2.1.95 ncr53c8xx driver version.
- Add SMP support for linux-2.1.95 and above.
- - Fix a bug when QUEUE FULL is returned and no commands are
- disconnected. This happens with Atlas I / L912 and may happen
+ - Fix a bug when QUEUE FULL is returned and no commands are
+ disconnected. This happens with Atlas I / L912 and may happen
with Atlas II / LXY4.
- - Nail another one on CHECK condition when requeuing the command
+ - Nail another one on CHECK condition when requeuing the command
for auto-sense.
- - Call scsi_done() for all completed commands after interrupt
+ - Call scsi_done() for all completed commands after interrupt
handling.
- Increase the done queue to 24 entries.
Sat Apr 4 20:00 1998 Gerard Roudier ([email protected])
* revision 2.6i
- - CTEST0 is used by the 53C885 for Power Management and
+ - CTEST0 is used by the 53C885 for Power Management and
priority setting between the 2 functions.
- Use SDID instead as actual target number. Just have had to
+ Use SDID instead as actual target number. Just have had to
overwrite it with SSID on reselection.
- Split DATA_IN and DATA_OUT scripts into 2 sub-scripts.
64 segments are moved from on-chip RAM scripts.
- If more segments, a script in main memory is used for the
+ If more segments, a script in main memory is used for the
additional segments.
- - Since the SCRIPTS processor continues SCRIPTS execution after
- having won arbitration, do some stuff prior to testing any SCSI
- phase on reselection. This should have the vertue to process
+ - Since the SCRIPTS processor continues SCRIPTS execution after
+ having won arbitration, do some stuff prior to testing any SCSI
+ phase on reselection. This should have the virtue to process
scripts in parallel with the SCSI core performing selection.
- Increase the done queue to 12 entries.
@@ -436,21 +436,21 @@ Tue Mar 26 23:00 1998 Gerard Roudier ([email protected])
- New done queue. 8 entries by default (6 always useable).
Can be increased if needed.
- Resources management using doubly linked queues.
- - New auto-sense and QUEUE FULL handling that does not need to
+ - New auto-sense and QUEUE FULL handling that does not need to
stall the NCR queue any more.
- New CCB starvation avoiding algorithm.
- - Prepare CCBs for SCSI commands that cannot be queued, instead of
- inserting these commands into the waiting list. The waiting list
- is now only used while resetting and when memory for CCBs is not
+ - Prepare CCBs for SCSI commands that cannot be queued, instead of
+ inserting these commands into the waiting list. The waiting list
+ is now only used while resetting and when memory for CCBs is not
yet available?
Sun Feb 8 22:00 1998 Gerard Roudier ([email protected])
* revision 2.6f
- - Some fixes in order to really support the 53C895, at least with
+ - Some fixes in order to really support the 53C895, at least with
FAST-20 devices.
- - Heavy changes in the target/lun resources management to allow
- the scripts to jump directly to the CCB on reselection instead
- of walking on the lun CCBs list. Up to 32 tags per lun are now
+ - Heavy changes in the target/lun resources management to allow
+ the scripts to jump directly to the CCB on reselection instead
+ of walking on the lun CCBs list. Up to 32 tags per lun are now
supported without script processor and PCI traffic overhead.
Sun Jan 11 22:00 1998 Gerard Roudier ([email protected])
@@ -458,14 +458,14 @@ Sun Jan 11 22:00 1998 Gerard Roudier ([email protected])
- new (different ?) implementation of the start queue:
Use a simple CALL to a launch script in the CCB.
- implement a minimal done queue (1 entry :-) ).
- this avoid scanning all CCBs on INT FLY (Only scan all CCBs, on
- overflow). Hit ratio is better than 99.9 % on my system, so no
+ this avoid scanning all CCBs on INT FLY (Only scan all CCBs, on
+ overflow). Hit ratio is better than 99.9 % on my system, so no
need to have a larger done queue.
- - generalization of the restart of CCB on special condition as
+ - generalization of the restart of CCB on special condition as
Abort, QUEUE FULL, CHECK CONDITION.
This has been called 'silly scheduler'.
- - make all the profiling code conditionned by a config option.
- This spare some PCI traffic and C code when this feature is not
+ - make all the profiling code conditioned by a config option.
+ This spare some PCI traffic and C code when this feature is not
needed.
- handle more cleanly the situation where direction is unknown.
The pointers patching is now performed by the SCRIPTS processor.
@@ -473,9 +473,9 @@ Sun Jan 11 22:00 1998 Gerard Roudier ([email protected])
Ported from driver 2.5 series:
------------------------------
- - Use FAST-5 instead of SLOW for slow scsi devices according to
+ - Use FAST-5 instead of SLOW for slow scsi devices according to
new SPI-2 draft.
- - Make some changes in order to accommodate with 875 rev <= 3
+ - Make some changes in order to accommodate with 875 rev <= 3
device errata listing 397. Minor consequences are:
. Leave use of PCI Write and Invalidate under user control.
Now, by default the driver does not enable PCI MWI and option
@@ -484,12 +484,12 @@ Sun Jan 11 22:00 1998 Gerard Roudier ([email protected])
. Programmed burst length set to 64 DWORDS (instead of 128).
(Note: SYMBIOS uses 32 DWORDS for the SDMS BIOS)
- Add 'buschk' boot option.
- This option enables checking of SCSI BUS data lines after SCSI
+ This option enables checking of SCSI BUS data lines after SCSI
RESET (set by default). (Submitted by Richard Waltham).
- Update the README file.
- - Dispatch CONDITION MET and RESERVATION CONFLICT scsi status
+ - Dispatch CONDITION MET and RESERVATION CONFLICT scsi status
as OK driver status.
- - Update the README file and the Symbios NVRAM format definition
+ - Update the README file and the Symbios NVRAM format definition
with removable media flags values (available with SDMS 4.09).
- Several PCI configuration registers fix-ups for powerpc.
(Patch sent by Cort).
--
2.26.3
s/preemptable/preemptible/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/trace/ftrace-uses.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/trace/ftrace-uses.rst b/Documentation/trace/ftrace-uses.rst
index f7d98ae5b885..2903a58f5ac2 100644
--- a/Documentation/trace/ftrace-uses.rst
+++ b/Documentation/trace/ftrace-uses.rst
@@ -193,7 +193,7 @@ FTRACE_OPS_FL_RECURSION
Not, if this flag is set, then the callback will always be called
with preemption disabled. If it is not set, then it is possible
(but not guaranteed) that the callback will be called in
- preemptable context.
+ preemptible context.
FTRACE_OPS_FL_IPMODIFY
Requires FTRACE_OPS_FL_SAVE_REGS set. If the callback is to "hijack"
--
2.26.3
s/assymetry/asymmetry/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/scheduler/sched-nice-design.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/scheduler/sched-nice-design.rst b/Documentation/scheduler/sched-nice-design.rst
index 0571f1b47e64..3511d86575e7 100644
--- a/Documentation/scheduler/sched-nice-design.rst
+++ b/Documentation/scheduler/sched-nice-design.rst
@@ -60,7 +60,7 @@ within the constraints of HZ and jiffies and their nasty design level
coupling to timeslices and granularity it was not really viable.
The second (less frequent but still periodically occurring) complaint
-about Linux's nice level support was its assymetry around the origo
+about Linux's nice level support was its asymmetry around the origo
(which you can see demonstrated in the picture above), or more
accurately: the fact that nice level behavior depended on the _absolute_
nice level as well, while the nice API itself is fundamentally
--
2.26.3
s/simultanously/simultaneously/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/scheduler/sched-bwc.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/scheduler/sched-bwc.rst b/Documentation/scheduler/sched-bwc.rst
index 845eee659199..a7f9be925ab8 100644
--- a/Documentation/scheduler/sched-bwc.rst
+++ b/Documentation/scheduler/sched-bwc.rst
@@ -133,7 +133,7 @@ average usage, albeit over a longer time window than a single period. This
also limits the burst ability to no more than 1ms per cpu. This provides
better more predictable user experience for highly threaded applications with
small quota limits on high core count machines. It also eliminates the
-propensity to throttle these applications while simultanously using less than
+propensity to throttle these applications while simultaneously using less than
quota amounts of cpu. Another way to say this, is that by allowing the unused
portion of a slice to remain valid across periods we have decreased the
possibility of wastefully expiring quota on cpu-local silos that don't need a
--
2.26.3
s/resonable/reasonable/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/riscv/pmu.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/riscv/pmu.rst b/Documentation/riscv/pmu.rst
index acb216b99c26..fde31b6aa861 100644
--- a/Documentation/riscv/pmu.rst
+++ b/Documentation/riscv/pmu.rst
@@ -168,7 +168,7 @@ counter (event->count), but also updates the left period to the next interrupt
But the core of perf does not need direct write to counters. Writing counters
is hidden behind the abstraction of 1) *pmu->start*, literally start counting so one
has to set the counter to a good value for the next interrupt; 2) inside the IRQ
-it should set the counter to the same resonable value.
+it should set the counter to the same reasonable value.
Reading is not a problem in RISC-V but writing would need some effort, since
counters are not allowed to be written by S-mode.
--
2.26.3
s/enhancments/enhancements/
Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
Documentation/openrisc/openrisc_port.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/openrisc/openrisc_port.rst b/Documentation/openrisc/openrisc_port.rst
index 657ac4af7be6..b3c6c5e258b0 100644
--- a/Documentation/openrisc/openrisc_port.rst
+++ b/Documentation/openrisc/openrisc_port.rst
@@ -114,7 +114,7 @@ History
port to 2.6.x
30-11-2004 Matjaz Breskvar ([email protected])
- lots of bugfixes and enhancments.
+ lots of bugfixes and enhancements.
added opencores framebuffer driver.
09-10-2010 Jonas Bonn ([email protected])
--
2.26.3
On Sun, Mar 28, 2021 at 10:37 PM Max Filippov <[email protected]> wrote:
>
> On Sun, Mar 28, 2021 at 10:18 PM Bhaskar Chowdhury
> <[email protected]> wrote:
> >
> > s/controlers/controllers/
> >
> > Signed-off-by: Bhaskar Chowdhury <[email protected]>
> > ---
> > Documentation/xtensa/atomctl.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/xtensa/atomctl.rst b/Documentation/xtensa/atomctl.rst
> > index 1ecbd0ba9a2e..a0efab2abe8f 100644
> > --- a/Documentation/xtensa/atomctl.rst
> > +++ b/Documentation/xtensa/atomctl.rst
> > @@ -23,7 +23,7 @@ doing a Cached (WB) transaction and use the Memory RCW for un-cached
> > operations.
> >
> > For systems without an coherent cache controller, non-MX, we always
> > -use the memory controllers RCW, thought non-MX controlers likely
> > +use the memory controllers RCW, thought non-MX controllers likely
>
> In this line you could also do s/thought/though/.
...and s/memory controllers/memory controller's/
--
Thanks.
-- Max
On Sun, Mar 28, 2021 at 10:18 PM Bhaskar Chowdhury
<[email protected]> wrote:
>
> s/controlers/controllers/
>
> Signed-off-by: Bhaskar Chowdhury <[email protected]>
> ---
> Documentation/xtensa/atomctl.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/xtensa/atomctl.rst b/Documentation/xtensa/atomctl.rst
> index 1ecbd0ba9a2e..a0efab2abe8f 100644
> --- a/Documentation/xtensa/atomctl.rst
> +++ b/Documentation/xtensa/atomctl.rst
> @@ -23,7 +23,7 @@ doing a Cached (WB) transaction and use the Memory RCW for un-cached
> operations.
>
> For systems without an coherent cache controller, non-MX, we always
> -use the memory controllers RCW, thought non-MX controlers likely
> +use the memory controllers RCW, thought non-MX controllers likely
In this line you could also do s/thought/though/.
--
Thanks.
-- Max
On 22:38 Sun 28 Mar 2021, Max Filippov wrote:
>On Sun, Mar 28, 2021 at 10:37 PM Max Filippov <[email protected]> wrote:
>>
>> On Sun, Mar 28, 2021 at 10:18 PM Bhaskar Chowdhury
>> <[email protected]> wrote:
>> >
>> > s/controlers/controllers/
>> >
>> > Signed-off-by: Bhaskar Chowdhury <[email protected]>
>> > ---
>> > Documentation/xtensa/atomctl.rst | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/Documentation/xtensa/atomctl.rst b/Documentation/xtensa/atomctl.rst
>> > index 1ecbd0ba9a2e..a0efab2abe8f 100644
>> > --- a/Documentation/xtensa/atomctl.rst
>> > +++ b/Documentation/xtensa/atomctl.rst
>> > @@ -23,7 +23,7 @@ doing a Cached (WB) transaction and use the Memory RCW for un-cached
>> > operations.
>> >
>> > For systems without an coherent cache controller, non-MX, we always
>> > -use the memory controllers RCW, thought non-MX controlers likely
>> > +use the memory controllers RCW, thought non-MX controllers likely
>>
>> In this line you could also do s/thought/though/.
>
>...and s/memory controllers/memory controller's/
>
Thanks, will do both the mentioned changes in V2..
>--
>Thanks.
>-- Max