From: Alan Mikhak <alan.mikhak@sifive.com>
To: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kishon@ti.com, lorenzo.pieralisi@arm.com,
linux-riscv@lists.infradead.org, palmer@sifive.com,
paul.walmsley@sifive.com
Subject: [PATCH v2 0/2] tools: PCI: Fix broken pcitest compilation
Date: Thu, 23 May 2019 14:17:59 -0700 [thread overview]
Message-ID: <1558646281-12676-1-git-send-email-alan.mikhak@sifive.com> (raw)
This patchset fixes a compiler error and two warnings that resulted in a
broken compilation of pcitest.
tools/pci/pcitest.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--
2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Alan Mikhak <alan.mikhak@sifive.com>
To: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kishon@ti.com, lorenzo.pieralisi@arm.com,
linux-riscv@lists.infradead.org, palmer@sifive.com,
paul.walmsley@sifive.com
Subject: [PATCH v2 0/2] tools: PCI: Fix broken pcitest compilation
Date: Thu, 23 May 2019 14:17:59 -0700 [thread overview]
Message-ID: <1558646281-12676-1-git-send-email-alan.mikhak@sifive.com> (raw)
This patchset fixes a compiler error and two warnings that resulted in a
broken compilation of pcitest.
tools/pci/pcitest.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--
2.7.4
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-05-23 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 21:17 Alan Mikhak [this message]
2019-05-23 21:17 ` [PATCH v2 0/2] tools: PCI: Fix broken pcitest compilation Alan Mikhak
2019-05-23 21:18 ` [PATCH v2 1/2] " Alan Mikhak
2019-05-23 21:18 ` Alan Mikhak
2019-05-23 21:18 ` [PATCH v2 2/2] tools: PCI: Fix compiler warning in pcitest Alan Mikhak
2019-05-23 21:18 ` Alan Mikhak
2019-05-29 16:59 ` [PATCH v2 0/2] tools: PCI: Fix broken pcitest compilation Lorenzo Pieralisi
2019-05-29 16:59 ` Lorenzo Pieralisi
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=1558646281-12676-1-git-send-email-alan.mikhak@sifive.com \
--to=alan.mikhak@sifive.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.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.