From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Philipp Hahn <hahn@univention.de>,
"Hao, Xudong" <xudong.hao@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Chris Wright <chrisw@sous-sol.org>,
"M. Mohan Kumar" <mohan@in.ibm.com>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH v5] virtio-9p: fix build on !CONFIG_UTIMENSAT
Date: Wed, 01 Dec 2010 10:16:15 +0900 [thread overview]
Message-ID: <4CF5A1DF.3050808@jp.fujitsu.com> (raw)
In-Reply-To: <4CECC642.8090404@redhat.com>
Ping.
Maintainers, please tell me if still something is required for
this patch before applying it.
Thanks,
H.Seto
(2010/11/24 17:01), Jes Sorensen wrote:
> On 11/24/10 03:38, Hidetoshi Seto wrote:
>> This patch introduce a fallback mechanism for old systems that do not
>> support utimensat(). This fix build failure with following warnings:
>>
>> hw/virtio-9p-local.c: In function 'local_utimensat':
>> hw/virtio-9p-local.c:479: warning: implicit declaration of function 'utimensat'
>> hw/virtio-9p-local.c:479: warning: nested extern declaration of 'utimensat'
>>
>> and:
>>
>> hw/virtio-9p.c: In function 'v9fs_setattr_post_chmod':
>> hw/virtio-9p.c:1410: error: 'UTIME_NOW' undeclared (first use in this function)
>> hw/virtio-9p.c:1410: error: (Each undeclared identifier is reported only once
>> hw/virtio-9p.c:1410: error: for each function it appears in.)
>> hw/virtio-9p.c:1413: error: 'UTIME_OMIT' undeclared (first use in this function)
>> hw/virtio-9p.c: In function 'v9fs_wstat_post_chmod':
>> hw/virtio-9p.c:2905: error: 'UTIME_OMIT' undeclared (first use in this function)
>>
>> [NOTE: At this time virtio-9p is only user of utimensat(), and is available
>> only when host is linux and CONFIG_VIRTFS is defined. So there are
>> no similar warning for win32. Please provide a wrapper for win32 in
>> oslib-win32.c if new user really requires it.]
>>
>> v5:
>> - Allow fallback on runtime
>> - Move qemu_utimensat() to oslib-posix.c
>> - Rebased on latest qemu.git
>> v4:
>> - Use tv_now.tv_usec
>> v3:
>> - Use better alternative handling for UTIME_NOW/OMIT
>> - Move qemu_utimensat() to cutils.c
>> V2:
>> - Introduce qemu_utimensat()
>>
>> Acked-by: Chris Wright <chrisw@sous-sol.org>
>> Acked-by: M. Mohan Kumar <mohan@in.ibm.com>
>> Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
>> ---
>> hw/virtio-9p-local.c | 4 ++--
>> oslib-posix.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
>> qemu-os-posix.h | 12 ++++++++++++
>> 3 files changed, 62 insertions(+), 2 deletions(-)
>
> Hi Hidetoshi,
>
> This looks good to me!
>
> Acked-by: Jes Sorensen <Jes.Sorensen@redhat.com>
>
> Cheers,
> Jes
next prev parent reply other threads:[~2010-12-01 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 2:38 [PATCH v5] virtio-9p: fix build on !CONFIG_UTIMENSAT Hidetoshi Seto
2010-11-24 8:01 ` Jes Sorensen
2010-12-01 1:16 ` Hidetoshi Seto [this message]
2010-12-01 18:17 ` [Qemu-devel] " Venkateswararao Jujjuri (JV)
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=4CF5A1DF.3050808@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=Jes.Sorensen@redhat.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=chrisw@sous-sol.org \
--cc=hahn@univention.de \
--cc=kvm@vger.kernel.org \
--cc=mohan@in.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=xudong.hao@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).