From: "Arnd Bergmann" <arnd@kernel.org>
To: "Sudeep Holla" <sudeep.holla@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>
Cc: arm <arm@kernel.org>, "SoC Team" <soc@kernel.org>,
ALKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] firmware: arm_ffa: Fix for v7.1
Date: Mon, 13 Apr 2026 08:23:58 +0200 [thread overview]
Message-ID: <45bc09d9-33e0-48c4-92a3-9bf8e64ef80a@app.fastmail.com> (raw)
In-Reply-To: <20260411-exotic-astonishing-piculet-0cd25e@sudeepholla>
On Sat, Apr 11, 2026, at 19:35, Sudeep Holla wrote:
> On Sat, Apr 11, 2026 at 10:49:50AM +0200, Krzysztof Kozlowski wrote:
>> On Tue, Apr 07, 2026 at 11:08:39AM +0100, Sudeep Holla wrote:
>> > ----------------------------------------------------------------
>> > Arm FF-A fix for v7.1
>> >
>> > Use the page aligned backing allocation size when computing the RXTX_MAP
>> > page count. This fixes FF-A RX/TX buffer registration on kernels built
>> > with 16K/64K PAGE_SIZE, where alloc_pages_exact() backs the buffer with a
>> > larger aligned span than the discovered minimum buffer size.
>>
>> Can we avoid per-driver trees or pulls? You do maintain also ARM SCMI
>> firmware driver, so this could be sent together? I think you also use
>> the same Git tree, right?
>
> Sure, I can put all of the firmware drivers I maintain together. I had
> for some reason assumed individual PR is preferred.
To me, that's a function of how complex the changes are and how
you describe them in the changelog text: If you have a lot of changes
for the merge window, having one branch per firmware type probably
works best, or even multiple ones if you have a series that implements
something new and a number of random changes do existing code.
If you have only a handful of bugfixes across multiple firmware
subsystems, a single 'firmware fixes' is less work for all of
us, with no loss of readability in the git history.
Arnd
next prev parent reply other threads:[~2026-04-13 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 10:08 [GIT PULL] firmware: arm_ffa: Fix for v7.1 Sudeep Holla
2026-04-11 8:49 ` Krzysztof Kozlowski
2026-04-11 17:35 ` Sudeep Holla
2026-04-13 6:23 ` Arnd Bergmann [this message]
2026-04-13 8:32 ` Sudeep Holla
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=45bc09d9-33e0-48c4-92a3-9bf8e64ef80a@app.fastmail.com \
--to=arnd@kernel.org \
--cc=arm@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@kernel.org \
--cc=sudeep.holla@kernel.org \
/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