diff options
| author | Dan Carpenter <dan.carpenter@oracle.com> | 2012-03-28 10:30:26 +0300 |
|---|---|---|
| committer | Sarah Sharp <sarah.a.sharp@linux.intel.com> | 2012-04-11 08:29:00 -0700 |
| commit | 3fc8206d3dca1550eb0a1f6e2a350881835954ba (patch) | |
| tree | d3c2f4651dc2835e1f2096ea761ec7aec5d72887 /firmware | |
| parent | 457a4f61f9bfc3ae76e5b49f30f25d86bb696f67 (diff) | |
| download | linux-3fc8206d3dca1550eb0a1f6e2a350881835954ba.tar.bz2 | |
xHCI: use gfp flags from caller instead of GFP_ATOMIC
The caller is allowed to specify the GFP flags for these functions.
We should prefer their flags unless we have good reason. For
example, if we take a spin_lock ourselves we'd need to use
GFP_ATOMIC. But in this case it's safe to use the callers GFP
flags.
The callers all pass GFP_ATOMIC here, so this change doesn't affect
how the kernel behaves but we may add other callers later and this
is a cleanup.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions