diff options
author | Dominik Brodowski <linux@dominikbrodowski.net> | 2009-10-18 23:51:09 +0200 |
---|---|---|
committer | Dominik Brodowski <linux@dominikbrodowski.net> | 2009-10-19 00:29:36 +0200 |
commit | 84897fc0524d7cbfc81d0bdf9f92ade6e3c3816b (patch) | |
tree | e24975ac12a1947c1a74dde7d23e795e27c41146 /drivers/regulator | |
parent | 30514ccfc5651b0b1eb27d5ac1cb580b152cd85f (diff) |
pcmcia: pccard_read_tuple and TUPLE_RETURN_COMMON cleanup
pccard_read_tuple(), which is only used by the PCMCIA core, should
handle TUPLE_RETURN_COMMON more sensibly: If a specific function (which
may be 0) is requested, set tuple.Attributes = 0 as was done in all
PCMCIA drivers. If, however, BIND_FN_ALL is requested, return the
"common" tuple. As to the callers of pccard_read_tuple():
- All calls to pcmcia_validate_cis() had set the "function" parameter to
BIND_FN_ALL. Therefore, remove the "function" parameter and make the
parameter to pccard_read_tuple explicit.
- Calls to CISTPL_VERS_1 and CISTPL_MANFID now set BIND_FN_ALL. This was
already the case for calls to CISTPL_LONGLINK_MFC.
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Diffstat (limited to 'drivers/regulator')
0 files changed, 0 insertions, 0 deletions