[gvfs] Update comment stating that it's fine to have a NULL GduDevice
- From: David Zeuthen <davidz src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gvfs] Update comment stating that it's fine to have a NULL GduDevice
- Date: Fri, 19 Feb 2010 19:23:56 +0000 (UTC)
commit 28cac0d0e24e8e3f58ef82503b5acedd7fc5b096
Author: David Zeuthen <davidz redhat com>
Date: Fri Feb 19 11:57:03 2010 -0500
Update comment stating that it's fine to have a NULL GduDevice
Signed-off-by: David Zeuthen <davidz redhat com>
monitor/gdu/ggdudrive.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
---
diff --git a/monitor/gdu/ggdudrive.c b/monitor/gdu/ggdudrive.c
index 72126a0..4607223 100644
--- a/monitor/gdu/ggdudrive.c
+++ b/monitor/gdu/ggdudrive.c
@@ -169,7 +169,9 @@ update_drive (GGduDrive *drive)
else
drive->name = gdu_presentable_get_name (drive->presentable);
- /* the GduDevice for an activatable drive (such as RAID) is NULL if the drive is not activated */
+ /* It's perfectly fine to not have a GduDevice - for example, this is the case for non-running
+ * MD RAID arrays as well as LVM2 Volume Group "drives"
+ */
if (device == NULL)
{
g_free (drive->device_file);
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]