From: Tom Rini <trini@konsulko.com>
To: Caleb Connolly <caleb.connolly@linaro.org>
Cc: "Neil Armstrong" <neil.armstrong@linaro.org>,
"Sumit Garg" <sumit.garg@linaro.org>,
"Varadarajan Narayanan" <quic_varada@quicinc.com>,
"Sam Day" <me@samcday.com>, "J . Neuschäfer" <j.ne@posteo.net>,
u-boot@lists.denx.de, u-boot-qcom@lists.denx.de
Subject: Re: [PULL] Please pull qcom/qcom-next
Date: Wed, 22 Jan 2025 15:57:00 -0600 [thread overview]
Message-ID: <20250122215700.GD60249@bill-the-cat> (raw)
In-Reply-To: <20250122162407.1870390-1-caleb.connolly@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Wed, Jan 22, 2025 at 05:17:45PM +0100, Caleb Connolly wrote:
> Hi Tom,
>
> The highlights are:
>
> * Fixed boot regression due to broken memory parsing
> * Enable HW RNG and KASLR on all platforms
> * Add support for Snapdragon X1 Elite hardware (clk/pinctrl)
> * Add support for QCS9100 ride automotive development platform (clk/ufs)
> * Add support for PCIe on SM8550, SM8650 and X1E
> * Implement software debounce for PMIC buttons
>
> Additionally, some minor improvements to "ufetch" have been pulled in:
>
> * Show CPU architecture (arm/mips/etc)
> * Make CONFIG_BLK optional
> * Fix 32-bit support
>
> The following changes since commit 82d262ae162d859d3b0bbcd40a9464e890b009da:
>
> Merge patch series "MediaTek MT7629 OF_UPSTREAM migration (v2)" (2025-01-21 09:29:05 -0600)
>
> are available in the Git repository at:
>
> git@source.denx.de:/u-boot/custodians/u-boot-snapdragon.git HEAD
>
> for you to fetch changes up to 599a1f9076d34c29d3683e0f833706478d62d9e0:
>
> MAINTAINERS: maintain qcs9100_defconfig (2025-01-22 17:14:24 +0100)
>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-01-22 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 16:17 [PULL] Please pull qcom/qcom-next Caleb Connolly
2025-01-22 21:57 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-04 14:22 Caleb Connolly
2024-10-04 17:15 ` Tom Rini
2024-10-04 14:17 Caleb Connolly
2024-10-04 14:21 ` Caleb Connolly
2024-09-09 10:04 Caleb Connolly
2024-09-09 10:14 ` Caleb Connolly
2024-09-09 19:45 ` Tom Rini
2024-03-01 15:45 Caleb Connolly
2024-03-01 21:35 ` 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=20250122215700.GD60249@bill-the-cat \
--to=trini@konsulko.com \
--cc=caleb.connolly@linaro.org \
--cc=j.ne@posteo.net \
--cc=me@samcday.com \
--cc=neil.armstrong@linaro.org \
--cc=quic_varada@quicinc.com \
--cc=sumit.garg@linaro.org \
--cc=u-boot-qcom@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.