From: "Jingoo Han" <jingoohan1@gmail.com>
To: "'Andy Shevchenko'" <andy.shevchenko@gmail.com>,
"'Niklas Cassel'" <niklas.cassel@axis.com>
Cc: "'Kishon Vijay Abraham I'" <kishon@ti.com>,
"'Joao Pinto'" <Joao.Pinto@synopsys.com>,
"'Lorenzo Pieralisi'" <lorenzo.pieralisi@arm.com>,
"'Bjorn Helgaas'" <bhelgaas@google.com>,
"'Niklas Cassel'" <niklass@axis.com>, <linux-pci@vger.kernel.org>,
"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] PCI: designware-ep: Return an error when requesting a too large BAR size
Date: Thu, 1 Feb 2018 14:00:40 -0500 [thread overview]
Message-ID: <000601d39b8e$f58a76f0$e09f64d0$@gmail.com> (raw)
In-Reply-To: <CAHp75VdX5=kzKFunM-Kbw7KOBt3+xik_pxhX1EZdO9eA3QHrBQ@mail.gmail.com>
On Thursday, February 1, 2018 1:58 PM, Andy Shevchenko wrote:
>
> On Thu, Feb 1, 2018 at 6:11 PM, Niklas Cassel <niklas.cassel@axis.com>
> wrote:
>
> include/linux/sizes.h:
>
> +SZ_4G 0x100000000ULL
>
> > + if (size > 0x100000000ULL) {
>
> #include <linux/sizes.h>
>
> if (size > SZ_4G) {
I like this one for the readability.
Thank you.
Best regards,
Jingoo Han
>
> ?
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2018-02-01 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 16:11 [PATCH 0/3] PCI endpoint 64-bit BAR fixes Niklas Cassel
2018-02-01 16:11 ` [PATCH 1/3] PCI: endpoint: Handle 64-bit BARs properly Niklas Cassel
2018-02-01 16:11 ` [PATCH 2/3] misc: pci_endpoint_test: " Niklas Cassel
2018-02-01 16:11 ` [PATCH 3/3] PCI: designware-ep: Return an error when requesting a too large BAR size Niklas Cassel
2018-02-01 18:57 ` Andy Shevchenko
2018-02-01 19:00 ` Jingoo Han [this message]
2018-02-05 16:25 ` Niklas Cassel
2018-02-06 19:38 ` Andy Shevchenko
2018-02-08 12:33 ` Niklas Cassel
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='000601d39b8e$f58a76f0$e09f64d0$@gmail.com' \
--to=jingoohan1@gmail.com \
--cc=Joao.Pinto@synopsys.com \
--cc=andy.shevchenko@gmail.com \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=niklas.cassel@axis.com \
--cc=niklass@axis.com \
/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.