Re: HDIO_DRIVE_CMD and hdparm

Alan Cox wrote:

  - SCSI doesn't handle HDIO_DRIVE_CMD(null), and returns EINVAL
    => fine for hdparm
  - If a block device doesn't support the ioctl, blkdev_driver_ioctl() returns
    ENOTTY
    => hdparm error message

Those are both correct
	-ENOTTY 		I don't know this ioctl
	-EINVAL			I know this ioctl, usage wrong

Exactly.
I'll have hdparm-7.4 not complain on ENOTTY as well.

-ml
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • HDIO_DRIVE_CMD and hdparm
    • From: Geert Uytterhoeven <[email protected]>
  • Re: HDIO_DRIVE_CMD and hdparm
    • From: Alan Cox <[email protected]>

• Prev by Date: Re: [patch 02/10] Linux Kernel Markers, architecture independent code.
• Next by Date: Re: [patch 07/10] Linux Kernel Markers - Documentation
• Previous by thread: Re: HDIO_DRIVE_CMD and hdparm
• Next by thread: Re: HDIO_DRIVE_CMD and hdparm
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]