qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Fam Zheng <famz@redhat.com>
Cc: "Kamil Rytarowski" <n54@gmx.com>,
	"Kamil Rytarowski" <kamil@netbsd.org>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Patrick Steinhardt" <ps@pks.im>,
	"Alistair Francis" <alistair23@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] 9pfs: include <linux/limits.h> for XATTR_SIZE_MAX
Date: Mon, 31 Jul 2017 15:31:44 +0100	[thread overview]
Message-ID: <CAFEAcA-96Be8PCs=zOD-w1LJ7Eed=HBvpqZrB+2AK8UdXutiaQ@mail.gmail.com> (raw)
In-Reply-To: <20170731142308.GB3206@lemon.lan>

On 31 July 2017 at 15:23, Fam Zheng <famz@redhat.com> wrote:
> No objection to adding more BSDs to patchew as long as I can find a few more
> gigabytes RAM to run the VM (BTW I'm also thinking about converting long running
> VMs to boot/shutdown on demand, to support more types of guests). But still want
> to ask this: how likely it is for a patch to compile on one BSD flavor but fail
> on the other?

I dunno about any particular patch, but when I came to trying
to get the BSDs into my test machine set I found that the
three different OSes were all failing for different reasons.
The bulk of "BSD fails" probably fail on all 3 though, so
you could probably get away with only testing 1 in patchew
and letting my tests catch the rest.

thanks
-- PMM

  reply	other threads:[~2017-07-31 14:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 19:20 [Qemu-devel] [PATCH] 9pfs: include <linux/limits.h> for XATTR_SIZE_MAX Patrick Steinhardt
2017-07-28 17:02 ` Alistair Francis
2017-07-28 17:20   ` Philippe Mathieu-Daudé
2017-07-29 13:50     ` Patrick Steinhardt
2017-07-29 19:34       ` Peter Maydell
2017-07-30 16:51         ` Kamil Rytarowski
2017-07-30 18:23           ` Peter Maydell
2017-07-30 23:07             ` Kamil Rytarowski
2017-07-31 14:23             ` Fam Zheng
2017-07-31 14:31               ` Peter Maydell [this message]
2017-07-31 14:36               ` Daniel P. Berrange
2017-07-31 14:52               ` Kamil Rytarowski
2017-08-11  6:52 ` Patrick Steinhardt

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='CAFEAcA-96Be8PCs=zOD-w1LJ7Eed=HBvpqZrB+2AK8UdXutiaQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alistair23@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=kamil@netbsd.org \
    --cc=n54@gmx.com \
    --cc=ps@pks.im \
    --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 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).