diff options
| author | keybuk@chromium.org <keybuk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-02-17 16:50:42 +0000 |
|---|---|---|
| committer | keybuk@chromium.org <keybuk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-02-17 16:50:42 +0000 |
| commit | 992079e0d0dd2d593bcadac28be4e2d15df75644 (patch) | |
| tree | 6aa924d193d3a89be2df4ffccbfcc3fb0d2d1072 /dbus/property.cc | |
| parent | 7fd47a85b9e070b1acbe4d6129f0edb9e3498099 (diff) | |
| download | chromium_src-992079e0d0dd2d593bcadac28be4e2d15df75644.zip chromium_src-992079e0d0dd2d593bcadac28be4e2d15df75644.tar.gz chromium_src-992079e0d0dd2d593bcadac28be4e2d15df75644.tar.bz2 | |
dbus: slight cleanup to Property code
Correct comments based on practice that worked best for the bluetooth
adapter and device clients, in particular adding the virtual destructor
to the struct and cleaning up the return values of GetObject() in the
documentation.
Drop VLOG() calls, there's no need to debug at this level, you can use
dbus-monitor to see the incoming and outgoing calls to Chromium and can
add logging in upper layers when there are real values to log.
BUG=none
TEST=built on try bots
Change-Id: I2ac6b55e288626b5f9cd843935887e261d386dec
Review URL: http://codereview.chromium.org/9418035
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122522 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'dbus/property.cc')
| -rw-r--r-- | dbus/property.cc | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/dbus/property.cc b/dbus/property.cc index 9d2adaf..0d6e7f0 100644 --- a/dbus/property.cc +++ b/dbus/property.cc @@ -59,9 +59,7 @@ void PropertySet::ConnectSignals() { void PropertySet::ChangedReceived(Signal* signal) { - VLOG(1) << "ChangedRecieved"; DCHECK(signal); - MessageReader reader(signal); std::string interface; @@ -106,7 +104,6 @@ void PropertySet::GetAll() { } void PropertySet::OnGetAll(Response* response) { - VLOG(1) << "OnGetAll"; if (!response) { LOG(WARNING) << "GetAll request failed."; return; |