From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 3/4] test: Add PCI device entry without compat string and with DT node
Date: Sun, 21 Oct 2018 21:31:00 -0400 [thread overview]
Message-ID: <20181022013100.GZ1032@bill-the-cat> (raw)
In-Reply-To: <20181010192709.19302-3-marek.vasut+renesas@gmail.com>
On Wed, Oct 10, 2018 at 09:27:08PM +0200, Marek Vasut wrote:
> Add PCI entry without compatible string and with a DT node only with
> reg = <...> property into the DT. This is needed for the tests to
> verify whether such a setup creates an U-Boot PCI device with the
> DT node associated with it in udevice.node.
>
> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
> Cc: Simon Glass <sjg@chromium.org>
> Cc: Tom Rini <trini@konsulko.com>
> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Applied to u-boot/master, 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/20181021/6711fb48/attachment.sig>
next prev parent reply other threads:[~2018-10-22 1:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 19:27 [U-Boot] [PATCH 1/4] pci: Support parsing PCI controller DT subnodes Marek Vasut
2018-10-10 19:27 ` [U-Boot] [PATCH 2/4] pci: Update documentation to make 'compatible' string optional Marek Vasut
2018-10-11 3:21 ` Bin Meng
2018-10-22 1:30 ` [U-Boot] [U-Boot, " Tom Rini
2018-10-10 19:27 ` [U-Boot] [PATCH 3/4] test: Add PCI device entry without compat string and with DT node Marek Vasut
2018-10-11 3:22 ` Bin Meng
2018-10-22 1:31 ` Tom Rini [this message]
2018-10-10 19:27 ` [U-Boot] [PATCH 4/4] test: Add test for PCI device " Marek Vasut
2018-10-11 3:22 ` Bin Meng
2018-10-22 1:31 ` [U-Boot] [U-Boot, " Tom Rini
2018-10-11 3:21 ` [U-Boot] [PATCH 1/4] pci: Support parsing PCI controller DT subnodes Bin Meng
2018-10-22 1:30 ` [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=20181022013100.GZ1032@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