Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/qemu: bump to latest version
Date: Wed, 27 Jul 2016 21:42:07 +0200	[thread overview]
Message-ID: <20160727214207.3477576e@free-electrons.com> (raw)
In-Reply-To: <1469483222-9091-1-git-send-email-gustavo@zacarias.com.ar>

Hello,

On Mon, 25 Jul 2016 18:47:02 -0300, Gustavo Zacarias wrote:
> Also bump the pc samples since they're tied to the (base) qemu config.
> 
> Results table:
> 
> Defconfig               Kernel  Qemu            Network Status
> --------------------------------------------------------------
> aarch64_virt            4.7     2.6.0           YES     OK (3)
> arm_versatile           4.7     2.5.0           YES     OK
> arm_vexpress            4.7     2.5.0           YES     OK
> m68k_mcf5208            4.7     2.5.0           YES     OK
> m68k_q800               4.7     q800-v2.4.0     NO (2)  OK
> microblazebe            4.7     2.5.0           YES     OK
> microblazeel            4.7     2.5.0           YES     OK
> mips32r2el_malta        4.7     2.5.0           YES     OK
> mips32r2_malta          4.7     2.5.0           YES     OK
> mips32r6el_malta        4.7     2.6.0           YES     OK (3)
> mips32r6_malta          4.7     2.6.0           YES     OK (3)
> mips64el_malta          4.7     2.5.0           YES     OK
> mips64_malta            4.7     2.5.0           YES     OK
> mips64r6el_malta        4.7     2.6.0           YES     OK (3)
> mips64r6_malta          4.7     2.6.0           YES     OK (3)
> ppc_g3beige             4.7     2.5.0           YES     OK
> ppc_mpc8544ds           4.7     2.5.0           YES     OK
> ppc_virtex_ml507        4.7     2.5.0           NO      OK
> ppc64_pseries           4.7     2.5.0           YES     OK
> sh4                     4.7     2.5.0           YES     OK
> sh4eb                   4.7     2.5.0           NO (1)  OK
> sparc_ss10              4.7     2.5.0           YES     OK
> sparc64_sun4u           4.7     2.5.0           YES     OK
> sparc_sun4u             4.7     2.5.0           YES     OK
> x86                     4.7     2.5.0           YES     OK
> x86_64                  4.7     2.5.0           YES     OK
> xtensa_lx60             4.7     2.6.0           YES     OK
> xtensa_lx60_nommu       4.7     2.6.0           YES     OK

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-07-27 19:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 21:47 [Buildroot] [PATCH] configs/qemu: bump to latest version Gustavo Zacarias
2016-07-27 19:42 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-04 20:30 Gustavo Zacarias
2016-06-04 22:14 ` Waldemar Brodkorb
2016-06-05 12:33   ` Gustavo Zacarias
2016-06-05 13:31     ` Waldemar Brodkorb
2016-06-05 13:32       ` Gustavo Zacarias
2016-06-06  2:06 ` Max Filippov
2016-06-06  2:07   ` Max Filippov
2016-06-06 23:24     ` Gustavo Zacarias
2016-06-07  3:16       ` Max Filippov
2016-06-07 10:43         ` Gustavo Zacarias

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=20160727214207.3477576e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox