diff options
| author |   Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | 2012-01-30 14:58:32 +0200 |
|---|---|---|
| committer |   David Woodhouse <David.Woodhouse@intel.com> | 2012-03-27 00:20:01 +0100 |
| commit | 3c3c10bba1e4ccb75b41442e45c1a072f6cded19 (patch) | |
| tree | 5c929e46cd0b6fcf8a42db7637cf45dbf69fe126 /drivers/mtd/chips/fwh_lock.h | |
| parent | jffs2: update to new MTD interface (diff) | |
| download | linux-dev-3c3c10bba1e4ccb75b41442e45c1a072f6cded19.tar.xz linux-dev-3c3c10bba1e4ccb75b41442e45c1a072f6cded19.zip | |
mtd: add leading underscore to all mtd functions
This patch renames all MTD functions by adding a "_" prefix:
mtd->erase -> mtd->_erase
mtd->read_oob -> mtd->_read_oob
...
The reason is that we are re-working the MTD API and from now on it is
an error to use MTD function pointers directly - we have a corresponding
API call for every pointer. By adding a leading "_" we achieve the following:
1. Make sure we convert every direct pointer users
2. A leading "_" suggests that this interface is internal and it becomes
less likely that people will use them directly
3. Make sure all the out-of-tree modules stop compiling and the owners
spot the big API change and amend them.
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'drivers/mtd/chips/fwh_lock.h')
| -rw-r--r-- | drivers/mtd/chips/fwh_lock.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/mtd/chips/fwh_lock.h b/drivers/mtd/chips/fwh_lock.h index 89c6595454a5..800b0e853e86 100644 --- a/drivers/mtd/chips/fwh_lock.h +++ b/drivers/mtd/chips/fwh_lock.h @@ -101,7 +101,7 @@ static void fixup_use_fwh_lock(struct mtd_info *mtd) { printk(KERN_NOTICE "using fwh lock/unlock method\n"); /* Setup for the chips with the fwh lock method */ - mtd->lock = fwh_lock_varsize; - mtd->unlock = fwh_unlock_varsize; + mtd->_lock = fwh_lock_varsize; + mtd->_unlock = fwh_unlock_varsize; } #endif /* FWH_LOCK_H */ |