All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
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 22:23:08 +0800	[thread overview]
Message-ID: <20170731142308.GB3206@lemon.lan> (raw)
In-Reply-To: <CAFEAcA9dvAnkKhKq03VccO1MLgg-4g20Mt2=85TZ1jF9XxHPRw@mail.gmail.com>

On Sun, 07/30 19:23, Peter Maydell wrote:
> On 30 July 2017 at 17:51, Kamil Rytarowski <n54@gmx.com> wrote:
> > On 29.07.2017 21:34, Peter Maydell wrote:
> >> On 29 July 2017 at 14:50, Patrick Steinhardt <ps@pks.im> wrote:
> >>> On Fri, Jul 28, 2017 at 02:20:49PM -0300, Philippe Mathieu-Daudé wrote:
> >>>> This is likely to break on BSD, but now than patchew has a NetBSD job
> >>>> you can trigger a build RESENDing this patch.
> >>
> >
> > I just checked patchew, and there is FreeBSD job. How far are we from
> > adding more BSDs?
> 
> I now test OpenBSD and NetBSD as well in my pre-merge
> test setup. Patchew could add them as well if desired.
> (vm setup instructions at http://wiki.qemu.org/Hosts/BSD)

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?

Fam

  parent reply	other threads:[~2017-07-31 14:23 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 [this message]
2017-07-31 14:31               ` Peter Maydell
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=20170731142308.GB3206@lemon.lan \
    --to=famz@redhat.com \
    --cc=alistair23@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=kamil@netbsd.org \
    --cc=n54@gmx.com \
    --cc=peter.maydell@linaro.org \
    --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 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.