From: Rob Herring <robherring2@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>
Subject: [GIT PULL] Devicetree fixes for 4.20-rc, round 2
Date: Fri, 9 Nov 2018 15:39:43 -0600 [thread overview]
Message-ID: <CAL_JsqLOqQ3p7mScZVfusQkrEvNCKzCWL+u1Jfe_d91Eh_krwQ@mail.gmail.com> (raw)
Linus,
Please pull.
Rob
The following changes since commit c961cb3be9064d1097ccc019390f8b5739daafc6:
of: Fix cpu node iterator to not ignore disabled cpu nodes
(2018-11-01 16:16:54 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
tags/devicetree-fixes-for-4.20-2
for you to fetch changes up to 89c38422e072bb453e3045b8f1b962a344c3edea:
of, numa: Validate some distance map rules (2018-11-08 12:44:34 -0600)
----------------------------------------------------------------
Devicetree fixes for 4.20-rc:
- Add validation of NUMA distance map to prevent crashes with bad map
- Fix setting of dma_mask
----------------------------------------------------------------
John Garry (1):
of, numa: Validate some distance map rules
Robin Murphy (1):
of/device: Really only set bus DMA mask when appropriate
drivers/of/device.c | 4 +++-
drivers/of/of_numa.c | 9 +++++++--
2 files changed, 10 insertions(+), 3 deletions(-)
next reply other threads:[~2018-11-09 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 21:39 Rob Herring [this message]
2018-11-09 22:45 ` [GIT PULL] Devicetree fixes for 4.20-rc, round 2 Linus Torvalds
2018-11-09 22:50 ` pr-tracker-bot
2018-11-14 0:55 ` 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=CAL_JsqLOqQ3p7mScZVfusQkrEvNCKzCWL+u1Jfe_d91Eh_krwQ@mail.gmail.com \
--to=robherring2@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).