From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] tmem: default to off
Date: Wed, 9 Jan 2019 13:28:19 -0500 [thread overview]
Message-ID: <20190109182819.GZ23427@char.us.oracle.com> (raw)
In-Reply-To: <20190109171617.uhgcap2fdqs34jkk@zion.uk.xensource.com>
On Wed, Jan 09, 2019 at 05:16:17PM +0000, Wei Liu wrote:
> On Wed, Jan 09, 2019 at 02:05:19AM -0700, Jan Beulich wrote:
> > As a short term alternative to deleting the code, default its building
> > to off (overridable in EXPERT mode only). Additionally make sure other
> > related baggage (LZO code) won't be carried when the option is off (with
> > TMEM scheduled to be deleted anyway, I didn't want to introduce a
> > separate Kconfig option to control the LZO compression code, and hence
> > CONFIG_TMEM is used directly there). Similarly I couldn't be bothered to
> > add actual content to the command line option doc for the two affected
> > options.
> >
> > Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> Acked-by: Wei Liu <wei.liu2@citrix.com>
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Thank you!
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-01-09 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 9:05 [PATCH] tmem: default to off Jan Beulich
2019-01-09 15:02 ` Roger Pau Monne
2019-01-09 15:27 ` Jan Beulich
2019-01-09 16:53 ` Roger Pau Monné
2019-01-09 17:16 ` Wei Liu
2019-01-09 18:28 ` Konrad Rzeszutek Wilk [this message]
[not found] <5C35B94F020000780020BB36@suse.com>
2019-01-09 9:09 ` Juergen Gross
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=20190109182819.GZ23427@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.