From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: "U-Boot Mailing List" <u-boot@lists.denx.de>,
"Marek Vasut" <marex@denx.de>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
"AKASHI Takahiro" <takahiro.akashi@linaro.org>,
"Marek Behún" <marek.behun@nic.cz>,
"Heinrich Schuchardt" <xypron.glpk@gmx.de>
Subject: Re: [PATCH v2 06/13] event: Add a simple test
Date: Thu, 10 Mar 2022 08:26:01 -0500 [thread overview]
Message-ID: <20220310132601.GD5020@bill-the-cat> (raw)
In-Reply-To: <20220304154308.2547711-7-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 217 bytes --]
On Fri, Mar 04, 2022 at 08:43:01AM -0700, Simon Glass wrote:
> Add a test for event registration and activation.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-03-10 13:26 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 15:42 [PATCH v2 00/13] event: Provide support for events to connect subsystems Simon Glass
2022-03-04 15:42 ` [PATCH v2 01/13] phy: nop-phy: Fix phy reset if no reset-gpio defined Simon Glass
2022-03-08 13:16 ` Heinrich Schuchardt
2022-03-04 15:42 ` [PATCH v2 02/13] Makefile: Allow LTO to be disabled for a build Simon Glass
2022-03-07 14:33 ` Tom Rini
2022-03-12 17:58 ` Simon Glass
2022-03-14 12:49 ` Tom Rini
2022-03-14 18:24 ` Simon Glass
2022-03-14 18:29 ` Tom Rini
2022-03-14 19:21 ` Simon Glass
2022-03-14 19:45 ` Tom Rini
2022-03-14 20:18 ` Simon Glass
2022-03-14 20:23 ` Tom Rini
2022-03-14 21:43 ` Simon Glass
2022-03-14 22:42 ` Tom Rini
2022-03-15 21:15 ` Simon Glass
2022-03-16 14:48 ` Tom Rini
2022-03-04 15:42 ` [PATCH v2 03/13] sandbox: start: Sort the header files Simon Glass
2022-03-10 13:25 ` Tom Rini
2022-03-04 15:42 ` [PATCH v2 04/13] binman: Expand elf support a little Simon Glass
2022-03-10 13:25 ` Tom Rini
2022-03-04 15:43 ` [PATCH v2 05/13] event: Add basic support for events Simon Glass
2022-03-07 4:26 ` AKASHI Takahiro
2022-03-08 16:05 ` Simon Glass
2022-03-10 13:25 ` Tom Rini
2022-03-04 15:43 ` [PATCH v2 06/13] event: Add a simple test Simon Glass
2022-03-10 13:26 ` Tom Rini [this message]
2022-03-04 15:43 ` [PATCH v2 07/13] event: Set up the event system on start-up Simon Glass
2022-03-10 13:26 ` Tom Rini
2022-03-04 15:43 ` [PATCH v2 08/13] event: Add events for device probe/remove Simon Glass
2022-03-10 13:26 ` Tom Rini
2022-03-04 15:43 ` [PATCH v2 09/13] event: Convert misc_init_f() to use events Simon Glass
2022-03-10 13:26 ` Tom Rini
2022-03-04 15:43 ` [PATCH v2 10/13] event: Convert arch_cpu_init_dm() " Simon Glass
2022-03-10 13:26 ` Tom Rini
2022-03-04 15:43 ` [PATCH v2 11/13] event: Add a command Simon Glass
2022-03-10 13:26 ` Tom Rini
2022-03-04 15:43 ` [PATCH v2 12/13] event: Add a script to decode the event-spy list Simon Glass
2022-03-10 13:26 ` Tom Rini
2022-03-04 15:43 ` [PATCH v2 13/13] event: Add documentation Simon Glass
2022-03-10 13:26 ` Tom Rini
2022-03-08 13:11 ` [PATCH v2 00/13] event: Provide support for events to connect subsystems Heinrich Schuchardt
2022-03-08 13:26 ` Tom Rini
2022-03-08 16:06 ` Simon Glass
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=20220310132601.GD5020@bill-the-cat \
--to=trini@konsulko.com \
--cc=marek.behun@nic.cz \
--cc=marex@denx.de \
--cc=sjg@chromium.org \
--cc=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=yamada.masahiro@socionext.com \
/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