Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: arm-soc <arm@kernel.org>, SoC <soc@kernel.org>
Cc: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	SoC list <soc@lists.linux.dev>
Subject: [GIT PULL 2/2] arm64: defconfig: TI K3 defconfig updates for v7.3
Date: Thu, 6 Aug 2026 21:33:26 +0530	[thread overview]
Message-ID: <52a08376-9942-4d5b-b8d8-c59df30de543@ti.com> (raw)
In-Reply-To: <42ae17e3-f40d-4825-a45c-5f046ef3159f@ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 843 bytes --]

The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:

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

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git tags/ti-k3-config-for-v7.3

for you to fetch changes up to ce17d88364bf0bf964eea2f99776896e10227454:

  arm64: defconfig: Enable drivers for BeagleBadge (2026-07-20 16:18:37 +0530)

----------------------------------------------------------------
TI K3 defconfig updates for v7.3

Board Specific Features
AM62L BeagleBadge:
- Enable drivers for components on BeagleBadge board

----------------------------------------------------------------
Judith Mendez (1):
      arm64: defconfig: Enable drivers for BeagleBadge

 arch/arm64/configs/defconfig | 5 +++++
 1 file changed, 5 insertions(+)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

      reply	other threads:[~2026-08-06 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 16:01 [GIT PULL 1/2] arm64: dts: ti: k3: DT updates for v7.3 Vignesh Raghavendra
2026-08-06 16:03 ` Vignesh Raghavendra [this message]

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=52a08376-9942-4d5b-b8d8-c59df30de543@ti.com \
    --to=vigneshr@ti.com \
    --cc=arm@kernel.org \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox