From: Logan Gunthorpe <logang@deltatee.com>
To: "Li, Philip" <philip.li@intel.com>,
"Wu, Fengguang" <fengguang.wu@intel.com>
Cc: Albert Ou <aou@eecs.berkeley.edu>, lkp <lkp@intel.com>,
"kbuild@lists.01.org" <kbuild@lists.01.org>,
Palmer Dabbelt <palmer@sifive.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zong Li <zongbox@gmail.com>, Olof Johansson <olof@lixom.net>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH 0/3] RISC-V: A few build/warning fixes and cleanup
Date: Thu, 1 Nov 2018 09:43:15 -0600 [thread overview]
Message-ID: <da34ca57-ea7b-7fb9-bc45-4b315513e43f@deltatee.com> (raw)
Message-ID: <20181101154315.sTCnkt0KXDOYYdr2mhvtX1VZcMSbnnVSIfQg7oZlmtk@z> (raw)
In-Reply-To: <831EE4E5E37DCC428EB295A351E662495131B2E7@shsmsx102.ccr.corp.intel.com>
On 2018-10-31 8:19 p.m., Li, Philip wrote:
>>> I think it would also be very nice to get the existing kbuild test robot
>>> to start compile testing a few riscv configs. It already does most of
> thanks Logan, the support to riscv and nds32 has been in our TODO list for
> a while, but whole team is blocked by other effort. We will focus on this soon
> to complete it within 2-3 weeks.
Thanks! Glad to hear it.
Logan
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-11-01 15:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 6:47 [PATCH 0/3] RISC-V: A few build/warning fixes and cleanup Olof Johansson
2018-10-31 6:47 ` Olof Johansson
2018-10-31 6:47 ` [PATCH 1/3] RISC-V: lib: Fix build error for 64-bit Olof Johansson
2018-10-31 6:47 ` Olof Johansson
2018-10-31 6:47 ` [PATCH 2/3] RISC-V: lib: minor asm cleanup Olof Johansson
2018-10-31 6:47 ` Olof Johansson
2018-10-31 6:47 ` [PATCH 3/3] RISC-V: Silence some module warnings on 32-bit Olof Johansson
2018-10-31 6:47 ` Olof Johansson
2018-10-31 17:09 ` [PATCH 0/3] RISC-V: A few build/warning fixes and cleanup Palmer Dabbelt
2018-10-31 17:09 ` Palmer Dabbelt
2018-10-31 17:52 ` Olof Johansson
2018-10-31 17:52 ` Olof Johansson
2018-10-31 18:12 ` Logan Gunthorpe
2018-10-31 18:12 ` Logan Gunthorpe
2018-11-01 1:43 ` Fengguang Wu
2018-11-01 1:43 ` Fengguang Wu
2018-11-01 2:19 ` Li, Philip
2018-11-01 2:19 ` Li, Philip
2018-11-01 15:43 ` Logan Gunthorpe [this message]
2018-11-01 15:43 ` Logan Gunthorpe
2018-11-01 16:17 ` Palmer Dabbelt
2018-11-01 16:17 ` Palmer Dabbelt
2018-11-01 17:20 ` Olof Johansson
2018-11-01 17:20 ` Olof Johansson
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=da34ca57-ea7b-7fb9-bc45-4b315513e43f@deltatee.com \
--to=logang@deltatee.com \
--cc=aou@eecs.berkeley.edu \
--cc=fengguang.wu@intel.com \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=olof@lixom.net \
--cc=palmer@sifive.com \
--cc=philip.li@intel.com \
--cc=zongbox@gmail.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).