summaryrefslogtreecommitdiffstats
path: root/drivers/ata
diff options
context:
space:
mode:
authorChengguang Xu <cgxu519@gmx.com>2019-02-10 23:19:01 +0800
committerJens Axboe <axboe@kernel.dk>2019-02-10 08:21:40 -0700
commit8d1e02d11e3d6ebffca26b29588cdbbe10b2ad39 (patch)
tree9968b49ab4559bc03dd3e99f9b11513941e6e7fa /drivers/ata
parent6c826b6867ab37689da61b4256705bdd370911da (diff)
downloadlinux-8d1e02d11e3d6ebffca26b29588cdbbe10b2ad39.tar.bz2
libata: fix a typo in comment
poitner -> pointer. Signed-off-by: Chengguang Xu <cgxu519@gmx.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/ata')
-rw-r--r--drivers/ata/libata-scsi.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/ata/libata-scsi.c b/drivers/ata/libata-scsi.c
index 3d4887d0e84a..c2adfd8486c4 100644
--- a/drivers/ata/libata-scsi.c
+++ b/drivers/ata/libata-scsi.c
@@ -2990,7 +2990,7 @@ static unsigned int atapi_xlat(struct ata_queued_cmd *qc)
* This inconsistency confuses several controllers which
* perform PIO using DMA such as Intel AHCIs and sil3124/32.
* These controllers use actual number of transferred bytes to
- * update DMA poitner and transfer of 4n+2 bytes make those
+ * update DMA pointer and transfer of 4n+2 bytes make those
* controller push DMA pointer by 4n+4 bytes because SATA data
* FISes are aligned to 4 bytes. This causes data corruption
* and buffer overrun.