From: Bandan Das <bsd@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Isaac Lozano <109lozanoi@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 2/2] usb-mtp: added object properties
Date: Tue, 15 Nov 2016 16:55:14 -0500 [thread overview]
Message-ID: <jpg37ise7ct.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <1473249360.28663.75.camel@redhat.com> (Gerd Hoffmann's message of "Wed, 07 Sep 2016 13:56:00 +0200")
Gerd Hoffmann <kraxel@redhat.com> writes:
> Hi,
>
>> and object properties. Most object properties are data that we already
>> have, except for the unique persistant object identifier. Windows
>
>> + case PROP_PERSISTENT_UNIQUE_OBJECT_IDENTIFIER:
>> + /* Should be persistant between sessions,
>> + * but using our objedt ID is "good enough"
>> + * for now */
>> + usb_mtp_add_u64(d, 0x0000000000000000);
>> + usb_mtp_add_u64(d, o->handle);
>> + break;
>
> Didn't I mention for an older version already that the inode number
> would be a better fit? The inode number is persistent and unique per
> filesystem. While being at it we might also add the device id, to
> handle the (unlikely) case that the mtp device spans multiple
> filesystems.
Seems Isaac is busy with school and stuff. I will pick these up and post
a follow up soon.
Bandan
> We stat() the file already and cache the result, so this is as simple as
> using o->stat.st_{dev,ino}. See "man 2 stat" for details.
>
> Other than that the patch series looks fine.
>
> Sorry for the delay. Now that vacation time, kvm forum and qemu 2.7
> freeze are over things should go faster for v4.
>
> cheers,
> Gerd
prev parent reply other threads:[~2016-11-15 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 10:06 [Qemu-devel] [PATCH v3 0/2] usb-mtp: Added support for sending files larger than 4gb Isaac Lozano
2016-08-06 10:06 ` [Qemu-devel] [PATCH v3 2/2] usb-mtp: added object properties Isaac Lozano
2016-09-07 11:56 ` Gerd Hoffmann
2016-11-15 21:55 ` Bandan Das [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jpg37ise7ct.fsf@linux.bootlegged.copy \
--to=bsd@redhat.com \
--cc=109lozanoi@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.