diff options
| author | Linus Walleij <linus.walleij@linaro.org> | 2017-02-01 15:47:52 +0300 |
|---|---|---|
| committer | Ulf Hansson <ulf.hansson@linaro.org> | 2017-02-13 15:20:57 +0300 |
| commit | acd8dbd64a2adcd950c31261247cda6f847f57eb (patch) | |
| tree | c2a5eba8e97dcf5cffcb6383cc1634e3cdddf47d /fs/drop_caches.c | |
| parent | db435505b561c1ca7b72c646dbc060f0c674360c (diff) | |
| download | linux-acd8dbd64a2adcd950c31261247cda6f847f57eb.tar.xz | |
mmc: block: rename rqc and req
In the function mmc_blk_issue_rw_rq() the new request coming in
from the block layer is called "rqc" and the old request that
was potentially just returned back from the asynchronous
mechanism is called "req".
This is really confusing when trying to analyze and understand
the code, it becomes a perceptual nightmare to me. Maybe others
have better parserheads but it is not working for me.
Rename "rqc" to "new_req" and "req" to "old_req" to reflect what
is semantically going on into the syntax.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'fs/drop_caches.c')
0 files changed, 0 insertions, 0 deletions