Linux SOC development
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>,
	ALKML <linux-arm-kernel@lists.infradead.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Arnd Bergmann <arnd@kernel.org>, Olof Johansson <olof@lixom.net>
Subject: [GIT PULL] firmware: arm_ffa: Fix for v6.6
Date: Wed, 27 Sep 2023 13:15:55 +0100	[thread overview]
Message-ID: <20230927121555.158619-1-sudeep.holla@arm.com> (raw)

Hi ARM SoC Team,

Please pull !

Regards,
Sudeep

-->8

The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:

  Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/ffa-fix-6.6

for you to fetch changes up to 9dda1178479aa0a73fe0eaabfe2d9a1c603cfeed:

  firmware: arm_ffa: Don't set the memory region attributes for MEM_LEND (2023-09-25 19:43:49 +0100)

----------------------------------------------------------------
Arm FF-A fix for v6.6

It has been reported that the driver sets the memory region attributes
for MEM_LEND operation when the specification clearly states not to. The
fix here addresses the issue by ensuring the memory region attributes are
cleared for the memory lending operation.

----------------------------------------------------------------
Sudeep Holla (1):
      firmware: arm_ffa: Don't set the memory region attributes for MEM_LEND

 drivers/firmware/arm_ffa/driver.c | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

             reply	other threads:[~2023-09-27 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 12:15 Sudeep Holla [this message]
2023-09-28  8:00 ` [GIT PULL] firmware: arm_ffa: Fix for v6.6 patchwork-bot+linux-soc
2023-09-28  8:01 ` patchwork-bot+linux-soc

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=20230927121555.158619-1-sudeep.holla@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=arm@kernel.org \
    --cc=arnd@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=soc@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