From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: u-boot@lists.denx.de
Subject: Re: [PULL] u-boot-sh/next
Date: Mon, 30 Dec 2024 15:52:56 -0600 [thread overview]
Message-ID: <20241230215256.GE3476@bill-the-cat> (raw)
In-Reply-To: <20241229173626.44743-1-marek.vasut+renesas@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
On Sun, Dec 29, 2024 at 06:35:50PM +0100, Marek Vasut wrote:
> The following changes since commit d580a013cca67a8115fb88d260498bde181709a1:
>
> Merge patch series "vbe: Series part E" (2024-12-27 15:16:39 -0600)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-sh.git next
>
> for you to fetch changes up to 678f7c8f560775e0ac33300f54281dfcaa2e525a:
>
> net: rswitch: Implement C22 to C45 access (2024-12-29 16:55:32 +0100)
>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-12-30 21:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 17:35 [PULL] u-boot-sh/next Marek Vasut
2024-12-30 21:52 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-18 20:33 Marek Vasut
2025-06-19 17:03 ` Tom Rini
2025-03-29 2:39 Marek Vasut
2025-03-30 14:16 ` Tom Rini
2025-03-19 23:48 Marek Vasut
2025-03-20 17:40 ` Tom Rini
2025-03-11 23:05 Marek Vasut
2025-03-12 13:55 ` Tom Rini
2025-02-26 19:33 Marek Vasut
2025-02-27 14:06 ` Tom Rini
2023-09-05 13:49 Marek Vasut
2023-09-06 17:50 ` Tom Rini
2023-03-18 16:52 Marek Vasut
2023-03-21 15:52 ` Tom Rini
2021-06-25 1:14 Marek Vasut
2021-06-25 1:22 ` Tom Rini
2021-06-25 1:25 ` Marek Vasut
2021-06-25 1:44 ` Tom Rini
2021-06-29 12:38 ` Tom Rini
2021-03-19 12:05 Marek Vasut
2021-03-19 14:30 ` Tom Rini
2020-10-01 8:28 Marek Vasut
2020-10-01 22:10 ` 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=20241230215256.GE3476@bill-the-cat \
--to=trini@konsulko.com \
--cc=marek.vasut+renesas@mailbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox