From: Fengguang Wu <fengguang.wu@intel.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Olof Johansson <olof@lixom.net>,
Palmer Dabbelt <palmer@sifive.com>,
linux-riscv@lists.infradead.org,
Albert Ou <aou@eecs.berkeley.edu>, Zong Li <zongbox@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kbuild@lists.01.org, kbuild test robot <lkp@intel.com>,
Philip Li <philip.li@intel.com>
Subject: Re: [PATCH 0/3] RISC-V: A few build/warning fixes and cleanup
Date: Thu, 1 Nov 2018 09:43:45 +0800 [thread overview]
Message-ID: <20181101014345.cdlte4grtaexb234@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <861817b9-c5f3-e995-2e18-9526d89d6561@deltatee.com>
CC Philip, current kbuild test robot maintainer.
On Wed, Oct 31, 2018 at 12:12:21PM -0600, Logan Gunthorpe wrote:
>
>On 2018-10-31 11:52 a.m., Olof Johansson wrote:
>> I've migrated machines to a new system and that CI is up and running.
>> Right now the emails don't go anywhere but me, but let me know where
>> you want them sent and I'll be happy to do so (probably not
>> linux-riscv due to volume/noise). They're also uploaded to
>> http://arm-soc.lixom.net/buildlogs/riscv/.
>>
>> Since you keep single-patch branches in your tree, and I compile
>> everything for every branch, I've restricted what branches I poll and
>> build. Right now it's "for*" and "riscv*".
>
>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
>the other arches. This would help us catch these kinds of issues even
>earlier seeing that test robot tests patches on mailing lists and many
>other repos before Palmer would even pull them into his branch.
>(Including a repo I routinely push branches to before sending out patches.)
>
>I'm not sure who's currently responsible for the robot but I've copied
>Fenguang who, I believe, set it up originally as well as the kbuild
>lists. Hopefully he can point us in the right direction to help get this
>set up.
>
>Thanks,
>
>Logan
>
next prev parent reply other threads:[~2018-11-01 1:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` [PATCH 2/3] RISC-V: lib: minor asm cleanup Olof Johansson
2018-10-31 6:47 ` [PATCH 3/3] RISC-V: Silence some module warnings on 32-bit 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:52 ` Olof Johansson
2018-10-31 18:12 ` Logan Gunthorpe
2018-11-01 1:43 ` Fengguang Wu [this message]
2018-11-01 2:19 ` Li, Philip
2018-11-01 15:43 ` Logan Gunthorpe
2018-11-01 16:17 ` Palmer Dabbelt
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=20181101014345.cdlte4grtaexb234@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=logang@deltatee.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
all inboxes | Powered by JetHome®