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/3] Renesas driver updates for v7.3
Date: Thu, 16 Jul 2026 12:03:42 +0200	[thread overview]
Message-ID: <cover.1784194405.git.geert+renesas@glider.be> (raw)
In-Reply-To: <cover.1784194401.git.geert+renesas@glider.be>

The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:

  Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git renesas-drivers-for-v7.3-tag1

for you to fetch changes up to 07231087d5e24c4d9c578c824b96f8af913f7324:

  soc: renesas: r8a78000: Drop duplicate "default ARCH_RENESAS" (2026-07-16 10:03:33 +0200)

----------------------------------------------------------------
Renesas driver updates for v7.3

  - Drop duplicate default for ARCH_R8A78000.

Note that this commit was just rebased, as I had accidentally queued it
on the wrong branch.

Thanks for pulling!

----------------------------------------------------------------
Geert Uytterhoeven (1):
      soc: renesas: r8a78000: Drop duplicate "default ARCH_RENESAS"

 drivers/soc/renesas/Kconfig | 1 -
 1 file changed, 1 deletion(-)


  parent reply	other threads:[~2026-07-16 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 10:03 [GIT PULL 0/3] Renesas SoC updates for v7.3 Geert Uytterhoeven
2026-07-16 10:03 ` [GIT PULL 1/3] Renesas ARM " Geert Uytterhoeven
2026-07-16 10:03 ` Geert Uytterhoeven [this message]
2026-07-16 10:03 ` [GIT PULL 3/3] Renesas DTS " Geert Uytterhoeven
2026-07-24 16:40 ` [GIT PULL 0/3] Renesas SoC " 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=cover.1784194405.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.