xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: Christian Lindig <christian.lindig@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Cc: Marcello Seri <marcello.seri@citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>,
	David Scott <dave@recoil.org>,
	John Thomson <git@johnthomson.fastmail.com.au>,
	Michael Young <m.a.young@durham.ac.uk>
Subject: Re: [PATCH 1/2] make xen ocaml safe-strings compliant
Date: Fri, 09 Feb 2018 11:06:00 +0100	[thread overview]
Message-ID: <1518170760.5629.110.camel@suse.com> (raw)
In-Reply-To: <EAB71B74-BDA5-49CD-9C55-6BB3BCDC3FB1@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1200 bytes --]

On Fri, 2018-02-09 at 09:20 +0000, Christian Lindig wrote:
> > On 8. Feb 2018, at 18:24, Wei Liu <wei.liu2@citrix.com> wrote:
> > 
> > Christian, do you have any idea when you can look into fixing the
> > safe-string patch?
> 
> Sorry, I can’t make a promise because of my other obligations. I do
> wonder, though: this patch did not come out of nowhere but supposedly
> was working - what is different here?
> 
Well, the only thing that I know about OCAML is that it is, for me as
an Italian, a word a little bit difficult to pronounce. :-D

But I'm happy to try to give some more details on what fails and how,
if you direct me. :-)

The testbox where this happens is a Debian unstable which has ocaml
4.05.0-10.

> In any case, I will reproduce the problem and take a look.
> 
Andrew said on IRC that he's seen something similar happening on some
of yours XenRT runs... but really, I'm happy to provide more info.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-02-09 10:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 22:55 [PATCH 1/2] make xen ocaml safe-strings compliant Michael Young
2018-02-06 16:49 ` Wei Liu
2018-02-06 21:56   ` Michael Young
2018-02-07 10:31     ` Wei Liu
2018-02-08 17:49 ` Dario Faggioli
2018-02-08 18:03   ` Wei Liu
2018-02-08 18:24     ` Wei Liu
2018-02-09  9:20       ` Christian Lindig
2018-02-09 10:06         ` Dario Faggioli [this message]
2018-02-12 14:55         ` Wei Liu
2018-03-09 22:57           ` Michael Young
2018-03-09 23:47             ` Christian Lindig
2018-03-10  0:36               ` Michael Young
2018-03-12 11:29             ` Christian Lindig
2018-03-12 19:35               ` Michael Young
2018-03-13  9:29                 ` Christian Lindig
2018-03-13 14:49                   ` Wei Liu
2018-02-13  0:35         ` Michael Young

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=1518170760.5629.110.camel@suse.com \
    --to=dfaggioli@suse.com \
    --cc=christian.lindig@citrix.com \
    --cc=dave@recoil.org \
    --cc=git@johnthomson.fastmail.com.au \
    --cc=m.a.young@durham.ac.uk \
    --cc=marcello.seri@citrix.com \
    --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 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).