On 01/31/2017 09:51 PM, James Bottomley wrote:
[1] which were a pain in the ass to untangle and debug during
development, it's really time for it to die..
Outside of the patch series in question, how to we expedite the
euthanasia of IDE? What explicit features/support are we missing
through libata that would need to be added, before we can git rm
drivers/ide/?
I thought the primary objection was actually embedded in that libata
Back at MontaVista, even embedded uses switched to libata years ago...
DaveM thinks we still can't prove that libata works everywhere the IDE works.
Besided, there are still a number of non-x86 drivers not converted over to
libata (like DaVinci, etc.)...
with its reliance on SCSI was just too large a dependency, so they have
to keep using drivers/ide.
Do you remember how many years ago a libata's own block driver was
promised to you? ;-)
I'd gladly wrote one, getting tired of my current OSS work... :-)
Perhaps nvme and flash is obviating this
problem and we can ask them again, though?
What's wrong with those? I'm not really following NVMe...
James
MBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-block" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
