From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] pci: Add boundary check for hose->regions
Date: Mon, 22 Apr 2019 09:52:47 -0400 [thread overview]
Message-ID: <20190422135247.GT4664@bill-the-cat> (raw)
In-Reply-To: <20190416163053.GA26165@ulmo>
On Tue, Apr 16, 2019 at 06:30:53PM +0200, Thierry Reding wrote:
> On Fri, Mar 15, 2019 at 04:32:32PM +0100, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > Make sure that we don't overflow the hose->regions array, otherwise we
> > would end up overwriting the hose->region_count field and cause mayhem
> > to ensue. Also print an error message when we'd be overflowing because
> > it indicates that there aren't enough regions available and the number
> > needs to be increased.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > drivers/pci/pci-uclass.c | 5 +++++
> > 1 file changed, 5 insertions(+)
>
> Hi Tom,
>
> have you had a chance to look at these two patches? Simon's reviewed
> them and they are needed to restore PCI support on Jetson TX2 (P2771).
They're on my list, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190422/b44f215a/attachment.sig>
next prev parent reply other threads:[~2019-04-22 13:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 15:32 [U-Boot] [PATCH 1/2] pci: Add boundary check for hose->regions Thierry Reding
2019-03-15 15:32 ` [U-Boot] [PATCH 2/2] pci: Scale MAX_PCI_REGIONS based on CONFIG_NR_DRAM_BANKS Thierry Reding
2019-03-22 7:53 ` Simon Glass
2019-04-24 13:27 ` [U-Boot] [U-Boot, " Tom Rini
2019-03-22 7:53 ` [U-Boot] [PATCH 1/2] pci: Add boundary check for hose->regions Simon Glass
2019-04-16 16:30 ` Thierry Reding
2019-04-22 13:52 ` Tom Rini [this message]
2019-04-24 13:27 ` [U-Boot] [U-Boot, " Tom Rini
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=20190422135247.GT4664@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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