From: Palmer Dabbelt <palmer@sifive.com>
To: linux-riscv@lists.infradead.org,
Alistair Francis <Alistair.Francis@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: [PATCH 0/3] RISC-V: defconfig: Cleanups and Generic PCIe Support
Date: Wed, 23 Jan 2019 14:50:22 -0800 [thread overview]
Message-ID: <20190123225025.32052-1-palmer@sifive.com> (raw)
This bounced around on the mailing list a handful of times. If there's
no opposition then I'll go ahead and put this in my next PR. I know the
split is a bit pedantic, but since everyone depends on defconfig I want
to be explicit about the changes.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-01-23 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 22:50 Palmer Dabbelt [this message]
2019-01-23 22:50 ` [PATCH 1/3] RISC-V: defconfig: Move CONFIG_PCI{,E_XILINX} Palmer Dabbelt
2019-01-23 22:50 ` [PATCH 2/3] RISC-V: defconfig: Enable Generic PCIE by default Palmer Dabbelt
2019-01-23 22:50 ` [PATCH 3/3] RISC-V: defconfig: Add CRYPTO_DEV_VIRTIO=y Palmer Dabbelt
2019-02-12 7:05 ` [PATCH 0/3] RISC-V: defconfig: Cleanups and Generic PCIe Support Christoph Hellwig
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=20190123225025.32052-1-palmer@sifive.com \
--to=palmer@sifive.com \
--cc=Alistair.Francis@wdc.com \
--cc=linux-riscv@lists.infradead.org \
--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 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).