All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: Simon Glass <sjg@chromium.org>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: Please pull u-boot-x86
Date: Mon, 27 Mar 2023 13:34:48 -0400	[thread overview]
Message-ID: <20230327173448.GC2040436@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmXnX2XzFQz8kbXG5zsd6+_dUr2NQTE5ZVQ4DeJrjiFa9Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

On Mon, Mar 27, 2023 at 09:42:25AM +0800, Bin Meng wrote:
> Hi Tom,

> 
> This PR contains the following x86 changes for v2023.04 release:
> 
> - x86: Bug fixes of previous BayTrail platform CONFIG_TEXT_BASE changes
> 
> The following changes since commit 8be7b4629e87ff8db08dd087c81d58129d029bad:
> 
>   Merge tag 'efi-2023.04-rc5' of
> https://source.denx.de/u-boot/custodians/u-boot-efi (2023-03-25
> 09:40:19 -0400)
> 
> are available in the Git repository at:
> 
>   https://source.denx.de/u-boot/custodians/u-boot-x86.git
> 
> for you to fetch changes up to 843e840dbacbf5b419f230d63f00990ac8efe7e4:
> 
>   x86: som-db5800-som-6867: Fix up adjustment of CONFIG_TEXT_BASE
> (2023-03-27 09:38:44 +0800)
> 

Applied to u-boot/master, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-03-27 17:35 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  1:42 Please pull u-boot-x86 Bin Meng
2023-03-27 17:34 ` Tom Rini [this message]
  -- 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
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-04  0:08 Bin Meng
2021-02-04 21:58 ` 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=20230327173448.GC2040436@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=bmeng.cn@gmail.com \
    --cc=sjg@chromium.org \
    --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.