From: Tom Rini <trini@konsulko.com>
To: Chris Packham <judge.packham@gmail.com>
Cc: u-boot@lists.denx.de, Dennis Gilmore <dgilmore@redhat.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Marek Behun <marek.behun@nic.cz>, Mario Six <mario.six@gdsys.cc>,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
Peng Fan <peng.fan@nxp.com>, Simon Glass <sjg@chromium.org>,
Stefan Roese <sr@denx.de>
Subject: Re: [PATCH 2/3] Convert CONFIG_FIXED_SDHCI_ALIGNED_BUFFER to Kconfig
Date: Mon, 6 Jun 2022 17:36:41 -0400 [thread overview]
Message-ID: <20220606213641.GG1958597@bill-the-cat> (raw)
In-Reply-To: <20220528231318.359510-2-judge.packham@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
On Sun, May 29, 2022 at 11:13:17AM +1200, Chris Packham wrote:
> CONFIG_FIXED_SDHCI_ALIGNED_BUFFER is needed on some Marvell SoCs when
> booting from MMC. All existing usages of this have the same value so
> make this the default and have the Kconfig option depend on SPL &&
> MVEBU_SPL_BOOT_DEVICE_MMC.
>
> Signed-off-by: Chris Packham <judge.packham@gmail.com>
> Reviewed-by: Marek Behún <marek.behun@nic.cz>
> Reviewed-by: Stefan Roese <sr@denx.de>
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-06-06 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 23:13 [PATCH 1/3] arm: mvebu: Use MVEBU_SPL_BOOT_DEVICE instead of SPL_BOOT_DEVICE Chris Packham
2022-05-28 23:13 ` [PATCH 2/3] Convert CONFIG_FIXED_SDHCI_ALIGNED_BUFFER to Kconfig Chris Packham
2022-05-29 10:47 ` Marek Behún
2022-05-30 6:52 ` Stefan Roese
2022-06-06 21:36 ` Tom Rini [this message]
2022-05-28 23:13 ` [PATCH 3/3] arm: mvebu: Remove CONFIG_SPL_BOOT_DEVICE Chris Packham
2022-05-29 10:47 ` Marek Behún
2022-05-30 6:53 ` Stefan Roese
2022-06-06 21:36 ` Tom Rini
2022-05-30 6:52 ` [PATCH 1/3] arm: mvebu: Use MVEBU_SPL_BOOT_DEVICE instead of SPL_BOOT_DEVICE Stefan Roese
2022-06-06 21:36 ` 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=20220606213641.GG1958597@bill-the-cat \
--to=trini@konsulko.com \
--cc=dgilmore@redhat.com \
--cc=jh80.chung@samsung.com \
--cc=judge.packham@gmail.com \
--cc=marek.behun@nic.cz \
--cc=mario.six@gdsys.cc \
--cc=patrick.delaunay@foss.st.com \
--cc=peng.fan@nxp.com \
--cc=sjg@chromium.org \
--cc=sr@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