All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: Please pull u-boot-x86
Date: Thu, 4 Feb 2021 08:08:51 +0800	[thread overview]
Message-ID: <CAEUhbmVDBMf1BwBM+Z0Mvhf+vojOV0dZoa0oJuXixn6Aj2okgw@mail.gmail.com> (raw)

Hi Tom,

This PR includes the following x86 changes for v2021.04:

- Fix broken multi-core boot for QEMU x86
- Add zboot support to boot x86 Linux kernel image in the PXE sysboot utility

Azure results: PASS
https://dev.azure.com/bmeng/GitHub/_build/results?buildId=320&view=results

The following changes since commit fdcb93e1709ab1a2ebb562455621617c29e2099c:

  Merge branch '2021-02-01-assorted-fixes' (2021-02-02 09:24:10 -0500)

are available in the git repository at:

  https://gitlab.denx.de/u-boot/custodians/u-boot-x86

for you to fetch changes up to 18c25821836b4673aa67a43c792a4a82480f47fa:

  cmd: pxe_utils: sysboot: Add zboot support to boot x86 Linux kernel
image (2021-02-03 23:16:44 +0800)

----------------------------------------------------------------
Bin Meng (1):
      x86: qemu: Fix broken multi-core boot

Kory Maincent (3):
      command.h: Remove extern from the header
      cmd: pxe_utils: Replace ifdef by IS_ENABLED
      cmd: pxe_utils: sysboot: Add zboot support to boot x86 Linux kernel image

 arch/x86/cpu/qfw_cpu.c |  6 ++++++
 cmd/pxe_utils.c        | 53
+++++++++++++++++++++++++++--------------------------
 include/command.h      | 57
++++++++++++++++++++++++++++++---------------------------
 3 files changed, 63 insertions(+), 53 deletions(-)

Regards,
Bin

             reply	other threads:[~2021-02-04  0:08 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04  0:08 Bin Meng [this message]
2021-02-04 21:58 ` Please pull u-boot-x86 Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2023-08-09 16:38 Bin Meng
2023-08-09 19:09 ` Tom Rini
2023-08-01 15:34 Bin Meng
2023-08-01 16:03 ` Tom Rini
2023-07-17 12:44 Bin Meng
2023-07-17 18:53 ` Tom Rini
2023-05-11  8:16 Bin Meng
2023-05-11 16:33 ` Tom Rini
2023-03-27  1:42 Bin Meng
2023-03-27 17:34 ` Tom Rini
2022-12-14  6:27 Bin Meng
2022-12-16 13:24 ` Tom Rini
2022-03-14 14:40 Bin Meng
2022-03-14 16:19 ` Tom Rini
2021-11-01  4:38 Bin Meng
2021-11-01 17:43 ` Tom Rini
2021-09-22 15:42 Bin Meng
2021-09-22 15:51 ` Tom Rini
2021-08-13  5:11 Bin Meng
2021-08-13 12:39 ` Tom Rini
2021-08-02 23:35 Bin Meng
2021-08-03 13:06 ` Tom Rini
2021-07-15 13:54 Bin Meng
2021-07-15 18:48 ` Tom Rini
2021-06-23 11:01 Bin Meng
2021-06-24 13:15 ` Tom Rini
2021-05-10 12:00 Bin Meng
2021-05-10 21:06 ` Tom Rini
2021-04-15  4:20 Bin Meng
2021-04-15 19:42 ` Tom Rini
2021-03-09  5:15 Bin Meng
2021-03-10  4:00 ` Tom Rini
2021-02-06 13:08 Bin Meng
2021-02-07 19:15 ` Tom Rini
2021-02-01  9:37 Bin Meng
2021-02-01 16:05 ` Tom Rini
2020-12-22  7:27 Bin Meng
2020-12-23 21:55 ` Tom Rini
2020-12-16  9:34 Bin Meng
2020-12-16 16:01 ` Tom Rini
2020-11-10  3:38 Bin Meng
2020-11-10 12:39 ` Tom Rini
2020-11-06  4:55 Bin Meng
2020-11-06 16:26 ` Tom Rini
2020-09-21 14:14 Bin Meng
2020-09-21 17:39 ` Tom Rini
2020-09-01 14:36 Bin Meng
2020-09-01 17:25 ` Tom Rini
2020-08-03  4:27 Bin Meng
2020-08-03 16:00 ` Tom Rini
2020-07-20  3:24 Bin Meng
2020-07-20 16:14 ` Tom Rini
2020-07-17 10:15 Bin Meng
2020-07-17 14:49 ` Tom Rini
2020-07-09  9:50 Bin Meng
2020-07-09 23:59 ` Tom Rini
2020-06-02  1:23 Bin Meng
2020-06-02 13:29 ` Tom Rini
2020-05-27  6:45 Bin Meng
2020-05-27 15:59 ` Tom Rini
2020-05-04  9:31 Bin Meng
2020-05-04 17:54 ` Tom Rini
2020-04-30 13:53 Bin Meng
2020-04-30 19:10 ` Tom Rini
2020-04-16 11:11 Bin Meng
2020-04-16 17:38 ` Tom Rini
2020-04-04 23:12 Bin Meng
2020-04-05 23:05 ` Tom Rini
2020-03-05 12:49 Bin Meng
2020-03-09 12:24 ` Tom Rini
2020-02-08  1:54 Bin Meng
2020-02-10 13:39 ` Tom Rini
2020-02-10 17:20   ` Anatolij Gustschin
2020-02-10 17:28     ` Tom Rini
2020-02-04  6:58 Bin Meng
2020-02-05  1:03 ` Tom Rini
2019-12-08 15:49 Bin Meng
2019-12-08 16:36 ` Tom Rini

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=CAEUhbmVDBMf1BwBM+Z0Mvhf+vojOV0dZoa0oJuXixn6Aj2okgw@mail.gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.