From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marex@denx.de>
Cc: u-boot@lists.denx.de
Subject: Re: [PULL] u-boot-usb/next
Date: Mon, 9 Sep 2024 22:08:07 -0600 [thread overview]
Message-ID: <20240910040807.GF4252@bill-the-cat> (raw)
In-Reply-To: <20240909202054.73857-1-marex@denx.de>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
On Mon, Sep 09, 2024 at 10:20:28PM +0200, Marek Vasut wrote:
> The following changes since commit d0f74bd417daf6492975ce346843ba0767caf51c:
>
> buildman: Support building within a Python venv (2024-09-06 12:45:54 -0600)
>
> are available in the Git repository at:
>
> git://source.denx.de/u-boot-usb.git next
>
> for you to fetch changes up to e72e683e36a83214dbb2547d88d553b5fd816dc8:
>
> phy: test: Implement sandbox PHY .set_mode and DM test (2024-09-09 17:18:04 +0200)
>
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-09-10 4:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 20:20 [PULL] u-boot-usb/next Marek Vasut
2024-09-10 4:08 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-05 12:59 Marek Vasut
2025-10-05 17:48 ` Tom Rini
2025-09-25 23:08 Marek Vasut
2025-09-26 15:56 ` Tom Rini
2025-03-17 3:15 Marek Vasut
2025-03-18 1:14 ` Tom Rini
2023-09-16 10:16 Marek Vasut
2023-09-16 22:38 ` Tom Rini
2023-09-05 13:50 Marek Vasut
2023-09-06 17:50 ` Tom Rini
2023-05-18 15:01 Marek Vasut
2023-05-18 20:09 ` Tom Rini
2023-03-03 0:05 Marek Vasut
2023-03-03 23:40 ` Tom Rini
2023-02-22 15:36 Marek Vasut
2023-02-22 18:37 ` Tom Rini
2023-02-22 22:09 ` Marek Vasut
2023-02-23 1:50 ` Tom Rini
2023-02-23 4:45 ` Marek Vasut
2023-02-23 16:36 ` Tom Rini
2020-10-01 8:29 Marek Vasut
2020-10-01 17:09 ` Tom Rini
2020-10-01 17:42 ` Marek Vasut
2020-10-01 18:09 ` Tom Rini
2020-10-01 18:38 ` Marek Vasut
2020-03-30 9:32 Marek Vasut
2020-04-01 13:43 ` 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=20240910040807.GF4252@bill-the-cat \
--to=trini@konsulko.com \
--cc=marex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox