From: Tom Rini <trini@konsulko.com>
To: Patrick Wildt <patrick@blueri.se>
Cc: Simon Glass <sjg@chromium.org>, Pratyush Yadav <p.yadav@ti.com>,
Jean-Jacques Hiblot <jjhiblot@ti.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH] mux: correct prototype for mux_control_try_select()
Date: Fri, 23 Jul 2021 08:34:47 -0400 [thread overview]
Message-ID: <20210723123447.GX9379@bill-the-cat> (raw)
In-Reply-To: <YO3/WmyXZfbj+jbf@mini.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
On Tue, Jul 13, 2021 at 11:02:18PM +0200, Patrick Wildt wrote:
> The macro should be passed a state, which should be passed
> to the actual function. Otherwise using that macro would
> yield a build error.
>
> Signed-off-by: Patrick Wildt <patrick@blueri.se>
> Reviewed-by: Pratyush Yadav <p.yadav@ti.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2021-07-23 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 21:02 [PATCH] mux: correct prototype for mux_control_try_select() Patrick Wildt
2021-07-14 8:12 ` Pratyush Yadav
2021-07-23 12:34 ` Tom Rini [this message]
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=20210723123447.GX9379@bill-the-cat \
--to=trini@konsulko.com \
--cc=jjhiblot@ti.com \
--cc=p.yadav@ti.com \
--cc=patrick@blueri.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox