In a reasonably good team, you should have a _queue_ of tasks assigned to you in an [issue tracker](http://programmers.stackexchange.com/tags/issue-tracking/info).

That way, while you are waiting for a reviewer, you could (_should_) work on next task waiting in that queue. Once you get used to work in that fashion, this will open an opportunity to have your changes reviewed in "batches", thus decreasing delays.

---

<sub>If you don't have such a "queue", discuss this with your manager, or better yet, with reviewer. If your team doesn't have reasonably convenient issue tracker for stuff like that, consider studying job boards or company internal job opportunities to find a better team (you might also discuss this with manager / reviewer but don't expect this to help - lack of a good issue tracker is often a symptom of something being severely broken in a team).</sub>