From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/qemu: Move patches to version directory
Date: Sat, 22 Jun 2019 10:18:21 +0200 [thread overview]
Message-ID: <20190622101821.4ef025b0@windsurf> (raw)
In-Reply-To: <20190604095605.7c9e7ef1@thl530.multi.box>
On Tue, 4 Jun 2019 09:56:05 +0200
Thomas Huth <huth@tuxfamily.org> wrote:
> At least the usbfs patch seems to be included in QEMU v4.0, so maybe it
> would be better to bump the version to 4.0 first?
Bumping to 4.0 would certainly be nice, but it really is a different
thing than what Guo is doing. Since it's not really necessary to add
support for C-SKY's Qemu version, I don't want to make bumping to 4.0 a
requirement for Guo's work.
> Thomas, did you ever send the first patch to upstream QEMU, too? Looks
> like a valid patch to me, so I think it should be accepted there,
> too...?
To be honest, I don't remember if I ever sent it upstream :-/
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Thomas Huth <huth@tuxfamily.org>
Cc: guoren@kernel.org, buildroot@buildroot.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-csky@vger.kernel.org, Guo Ren <ren_guo@c-sky.com>,
zhiwei_liu@c-sky.com,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/qemu: Move patches to version directory
Date: Sat, 22 Jun 2019 10:18:21 +0200 [thread overview]
Message-ID: <20190622101821.4ef025b0@windsurf> (raw)
In-Reply-To: <20190604095605.7c9e7ef1@thl530.multi.box>
On Tue, 4 Jun 2019 09:56:05 +0200
Thomas Huth <huth@tuxfamily.org> wrote:
> At least the usbfs patch seems to be included in QEMU v4.0, so maybe it
> would be better to bump the version to 4.0 first?
Bumping to 4.0 would certainly be nice, but it really is a different
thing than what Guo is doing. Since it's not really necessary to add
support for C-SKY's Qemu version, I don't want to make bumping to 4.0 a
requirement for Guo's work.
> Thomas, did you ever send the first patch to upstream QEMU, too? Looks
> like a valid patch to me, so I think it should be accepted there,
> too...?
To be honest, I don't remember if I ever sent it upstream :-/
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-22 8:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 12:28 [Buildroot] [PATCH 1/2] package/qemu: Move patches to version directory guoren at kernel.org
2019-06-03 12:28 ` guoren
2019-06-03 12:28 ` [Buildroot] [PATCH 2/2] package/qemu: Add C-SKY qemu support guoren at kernel.org
2019-06-03 12:28 ` guoren
2019-06-12 5:49 ` [Buildroot] " Guo Ren
2019-06-12 5:49 ` Guo Ren
2019-06-04 7:56 ` [Buildroot] [PATCH 1/2] package/qemu: Move patches to version directory Thomas Huth
2019-06-04 7:56 ` Thomas Huth
2019-06-04 8:34 ` Guo Ren
2019-06-04 8:34 ` Guo Ren
2019-06-22 8:18 ` Thomas Petazzoni [this message]
2019-06-22 8:18 ` Thomas Petazzoni
2019-06-22 15:49 ` Thomas Petazzoni
2019-06-22 15:49 ` Thomas Petazzoni
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=20190622101821.4ef025b0@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.