aboutsummaryrefslogtreecommitdiff
path: root/drivers/atm
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2007-12-25 19:17:00 +0200
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2007-12-26 19:15:17 +0200
commitd1f3dd6cc00f5bf744118fb2820ecdf09a1f4b73 (patch)
tree48663606422eda9245c3a53f1437f9c4458b8aa7 /drivers/atm
parent783b273afab43437dca731a229d53d72faf77fd3 (diff)
UBI: fix mtd device string parsing
UBI allows to specify MTD device name or number when the module is being loaded. When parsing MTD device identity string, it first tries to treat it as device NAME, and if that fails, it treats it as device number. Make it vice-versa as this is more logical and makes less troubles when you have an MTD device named "1" and try to load mtd1 which has different name. This is especially easy to hit when gluebi is enabled. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Diffstat (limited to 'drivers/atm')
0 files changed, 0 insertions, 0 deletions