All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: soc@lists.linux.dev, soc <soc@kernel.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL 2/5] Renesas ARM SoC updates for v6.15
Date: Fri, 21 Feb 2025 17:57:23 +0100	[thread overview]
Message-ID: <cover.1740156740.git.geert+renesas@glider.be> (raw)
In-Reply-To: <cover.1740156736.git.geert+renesas@glider.be>

The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:

  Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git tags/renesas-arm-soc-for-v6.15-tag1

for you to fetch changes up to 490a6291b17fbc65e31c54a0fd9301669ad283c0:

  ARM: shmobile: rcar-gen2: Remove CMA reservation code (2025-02-03 11:04:28 +0100)

----------------------------------------------------------------
Renesas ARM SoC updates for v6.15

  - Remove the legacy CMA reservation code on R-Car Gen2, which causes
    issues with highmem.

----------------------------------------------------------------
Geert Uytterhoeven (1):
      ARM: shmobile: rcar-gen2: Remove CMA reservation code

 arch/arm/mach-shmobile/setup-rcar-gen2.c | 76 --------------------------------
 1 file changed, 76 deletions(-)


  parent reply	other threads:[~2025-02-21 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 16:57 [GIT PULL 0/5] Renesas SoC updates for v6.15 Geert Uytterhoeven
2025-02-21 16:57 ` [GIT PULL 1/5] Renesas ARM defconfig " Geert Uytterhoeven
2025-02-21 16:57 ` Geert Uytterhoeven [this message]
2025-02-21 16:57 ` [GIT PULL 3/5] Renesas driver " Geert Uytterhoeven
2025-02-21 16:57 ` [GIT PULL 4/5] Renesas DT binding " Geert Uytterhoeven
2025-02-21 16:57 ` [GIT PULL 5/5] Renesas DTS " Geert Uytterhoeven

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=cover.1740156740.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=soc@kernel.org \
    --cc=soc@lists.linux.dev \
    /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.