From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: mprivozn@redhat.com, qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-ga: add guest-fstrim command
Date: Wed, 13 Jun 2012 07:31:45 +0200 [thread overview]
Message-ID: <4FD825C1.3020802@redhat.com> (raw)
In-Reply-To: <20120612210536.GB11828@illuin>
Il 12/06/2012 23:05, Michael Roth ha scritto:
> The FsMount* stuff is still only declared if CONFIG_FSFREEZE is defined,
> we'll need to make sure those are declared when CONFIG_FSTRIM is defined
> as well.
Shouldn't be a problem in practice as FIFREEZE is older:
fcccf502 (Takashi Sato 2009-01-09 16:40:59 -0800 332) #define FIFREEZE _IOWR('X', 119, int) /* Freeze */
fcccf502 (Takashi Sato 2009-01-09 16:40:59 -0800 333) #define FITHAW _IOWR('X', 120, int) /* Thaw */
367a51a3 (Lukas Czerner 2010-10-27 21:30:11 -0400 334) #define FITRIM _IOWR('X', 121, struct fstrim_range) /* Trim */
but I will fix it together with the version number.
Paolo
next prev parent reply other threads:[~2012-06-13 5:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 10:50 [Qemu-devel] [PATCH 0/2] qemu-ga: Add guest-fstrim command Paolo Bonzini
2012-06-12 10:50 ` [Qemu-devel] [PATCH 1/2] qemu-ga: make names more generic for mount list functions Paolo Bonzini
2012-06-12 10:50 ` [Qemu-devel] [PATCH 2/2] qemu-ga: add guest-fstrim command Paolo Bonzini
2012-06-12 19:54 ` Luiz Capitulino
2012-06-12 21:05 ` Michael Roth
2012-06-13 5:31 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-21 23:04 [Qemu-devel] [PULL] qemu-ga patches for " Michael Roth
2012-06-21 23:04 ` [Qemu-devel] [PATCH 2/2] qemu-ga: add " Michael Roth
2012-06-22 17:48 ` Chris Wedgwood
2012-06-22 21:12 ` Michael Roth
2012-06-23 3:38 ` Chris Wedgwood
2012-06-23 20:54 ` Michael Roth
2012-06-24 16:33 ` Christoph Hellwig
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=4FD825C1.3020802@redhat.com \
--to=pbonzini@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mprivozn@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.