All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Saravana Kannan <saravanak@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [GIT PULL] Devicetree fixes for v7.2, part 1
Date: Fri, 31 Jul 2026 15:45:57 -0500	[thread overview]
Message-ID: <20260731204557.GA1777195-robh@kernel.org> (raw)

Linus,

Please pull a couple of DT fixes for 7.2.

Rob

The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:

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

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devicetree-fixes-for-7.2

for you to fetch changes up to bba13ad17b1a11b3f1ed9b3a5d556191d7755a59:

  of/address: Fix NULL bus dereference in of_pci_range_parser_one() (2026-07-28 10:34:37 -0500)

----------------------------------------------------------------
Devicetree fixes for v7.2, part 1:

- Fix NULL bus dereference in of_pci_range_parser_one()

- Prevent OOB access when too many dynamic reserved memory regions are
  defined

----------------------------------------------------------------
Carlo Caione (1):
      of/address: Fix NULL bus dereference in of_pci_range_parser_one()

Sang-Heon Jeon (1):
      of: reserved_mem: prevent OOB when too many dynamic regions are defined

 drivers/of/address.c         | 22 ++++++++++++++++------
 drivers/of/of_reserved_mem.c | 14 +++++++++++---
 2 files changed, 27 insertions(+), 9 deletions(-)

             reply	other threads:[~2026-07-31 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 20:45 Rob Herring [this message]
2026-07-31 21:17 ` [GIT PULL] Devicetree fixes for v7.2, part 1 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-06-26 13:38 Rob Herring
2026-06-26 20:01 ` pr-tracker-bot

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=20260731204557.GA1777195-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saravanak@kernel.org \
    --cc=torvalds@linux-foundation.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 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.