tree 23be8fd1399ab90111e185714a03c5fb54ab45ea
parent f9bcb6dc8013d4da6660556ddf2383e4fbcbe3d7
author Frans Klaver <fransklaver@gmail.com> 1433968695 +0200
committer Brian Norris <computersforpeace@gmail.com> 1444753272 -0700

mtd: core: tone down suggestion that dev.parent should be set

add_mtd_device() has a comment suggesting that the caller should have
set dev.parent. This is required to have the parent device symlink show
up in sysfs, but not for proper operation of the mtd device itself.
Currently we have five drivers registering mtd devices during module
initialization, so they don't actually provide a parent device to link
to. That means we cannot WARN_ON() here, as it would trigger false
positives.

Make the comment a bit less firm in its assertion that dev.parent should
be set.

Signed-off-by: Frans Klaver <fransklaver@gmail.com>
Signed-off-by: Brian Norris <computersforpeace@gmail.com>