All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Anatolij Gustschin <agust@denx.de>
Cc: u-boot@lists.denx.de
Subject: Re: Please pull u-boot-video/next
Date: Mon, 28 Mar 2022 19:37:01 -0400	[thread overview]
Message-ID: <20220328233701.GL14476@bill-the-cat> (raw)
In-Reply-To: <20220328223752.1f4e9473@crub>

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

On Mon, Mar 28, 2022 at 10:37:52PM +0200, Anatolij Gustschin wrote:

> Hi Tom,
> 
> please pull video patches for next.
> 
> CI: https://source.denx.de/u-boot/custodians/u-boot-video/-/pipelines/11483
> 
> Thanks,
> Anatolij
> 
> The following changes since commit 34d2b7f20369d62c0f091d6572a8c0ea4655cf14:
> 
>   Merge tag 'v2022.04-rc5' into next (2022-03-28 12:36:49 -0400)
> 
> are available in the Git repository at:
> 
>   https://source.denx.de/u-boot/custodians/u-boot-video.git tags/next-20220328
> 
> for you to fetch changes up to 60cc4094485bf44b5ad455b51076f0e07f3f793a:
> 
>   video: Drop CONFIG_LCD_BMP_RLE8 (2022-03-28 20:30:33 +0200)
> 

Applied to u-boot/next, thanks!

-- 
Tom

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

  reply	other threads:[~2022-03-28 23:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 20:37 Please pull u-boot-video/next Anatolij Gustschin
2022-03-28 23:37 ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-07 16:16 Anatolij Gustschin
2023-03-07 20:06 ` Tom Rini
2021-12-28 14:25 Anatolij Gustschin
2022-01-01  4:51 ` Tom Rini
2020-06-18 20:54 Anatolij Gustschin
2020-06-19 13:24 ` 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=20220328233701.GL14476@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=agust@denx.de \
    --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.