From: Linus Walleij <linus.walleij@linaro.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Ansuel Smith <ansuelsmth@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
Russell King <linux@armlinux.org.uk>,
Jonathan Corbet <corbet@lwn.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Abbott Liu <liuwenliang@huawei.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: Enlarge IO_SPACE_LIMIT needed for some SoC
Date: Mon, 17 May 2021 12:26:02 +0200 [thread overview]
Message-ID: <CACRpkdYM5Rk9qxhkpsWqaGp-uZDoHJ3_r0605vC9SLQw6=BCAQ@mail.gmail.com> (raw)
In-Reply-To: <CAMj1kXGLihr4gq3iwHy6mLKG4UHWnh5XAgxZDZmnmNPErfJ-bg@mail.gmail.com>
On Tue, May 11, 2021 at 6:26 AM Ard Biesheuvel <ardb@kernel.org> wrote:
> I used to carry a PCIe serial port
> card to UEFI plugfests because that was the only thing that would stop
> working if a system configured its I/O resource window incorrectly
I've been looking for a thing like that for testing, I was actually
thinking that it would perhaps be a good idea to add a I/O-resource
requiring device to QEMU just to be able to test this kind of
thing for completeness.
Yours,
Linus Walleij
next prev parent reply other threads:[~2021-05-17 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 2:16 [PATCH] arm: Enlarge IO_SPACE_LIMIT needed for some SoC Ansuel Smith
2021-05-11 2:24 ` Matthew Wilcox
2021-05-11 2:32 ` Ansuel Smith
2021-05-11 4:26 ` Ard Biesheuvel
2021-05-11 12:15 ` Ansuel Smith
2021-05-11 12:30 ` Ard Biesheuvel
2021-05-11 12:37 ` Ansuel Smith
2021-05-11 12:46 ` Ard Biesheuvel
2021-05-11 12:51 ` Ansuel Smith
2021-05-11 14:55 ` Russell King - ARM Linux admin
2021-05-11 14:54 ` Russell King - ARM Linux admin
2021-05-17 10:26 ` Linus Walleij [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-28 14:44 Ansuel Smith
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='CACRpkdYM5Rk9qxhkpsWqaGp-uZDoHJ3_r0605vC9SLQw6=BCAQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=ansuelsmth@gmail.com \
--cc=ardb@kernel.org \
--cc=corbet@lwn.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liuwenliang@huawei.com \
--cc=mcgrof@kernel.org \
--cc=palmerdabbelt@google.com \
--cc=willy@infradead.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).