|
Remove IOThread::message_loop().
Instead introduce BrowserThread::UnsafeGetMessageLoop which is used in
a couple of places. This will be removed in a follow-up change. I
could have used UnsafeGetBrowserThread(id)->message_loop() but this is
even easier to search for.
Also, remove a couple of BrowserProcess accessors that aren't used by anybody, and that were using UnsafeGetBrowserThread.
TBR=battre@chromium.org
BUG= 98716
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=112697
|
Unified diffs |
Side-by-side diffs |
Delta from patch set |
Stats (+43 lines, -51 lines) |
Patch |
 |
M |
chrome/browser/browser_process.h
|
View
|
|
1 chunk |
+0 lines, -3 lines |
0 comments
|
Download
|
 |
M |
chrome/browser/browser_process_impl.h
|
View
|
|
2 chunks |
+0 lines, -3 lines |
0 comments
|
Download
|
 |
M |
chrome/browser/browser_process_impl.cc
|
View
|
|
2 chunks |
+2 lines, -11 lines |
0 comments
|
Download
|
 |
M |
chrome/browser/io_thread.h
|
View
|
|
2 chunks |
+1 line, -7 lines |
0 comments
|
Download
|
 |
M |
chrome/browser/io_thread.cc
|
View
|
|
3 chunks |
+6 lines, -9 lines |
0 comments
|
Download
|
 |
M |
chrome/browser/net/proxy_service_factory.cc
|
View
|
|
1 chunk |
+2 lines, -2 lines |
0 comments
|
Download
|
 |
M |
chrome/browser/process_singleton_linux.cc
|
View
|
|
1 chunk |
+7 lines, -9 lines |
0 comments
|
Download
|
 |
M |
chrome/test/base/testing_browser_process.h
|
View
|
|
1 chunk |
+0 lines, -1 line |
0 comments
|
Download
|
 |
M |
chrome/test/base/testing_browser_process.cc
|
View
|
|
1 chunk |
+0 lines, -4 lines |
0 comments
|
Download
|
 |
M |
content/browser/browser_thread_impl.cc
|
View
|
|
1 chunk |
+4 lines, -0 lines |
0 comments
|
Download
|
 |
M |
content/public/browser/browser_thread.h
|
View
|
|
3 chunks |
+21 lines, -2 lines |
0 comments
|
Download
|
Total messages: 8 (0 generated)
|