From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 108009 invoked by alias); 8 Aug 2018 17:41:56 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 107998 invoked by uid 89); 8 Aug 2018 17:41:56 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mail-wm0-f65.google.com Received: from mail-wm0-f65.google.com (HELO mail-wm0-f65.google.com) (74.125.82.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 08 Aug 2018 17:41:54 +0000 Received: by mail-wm0-f65.google.com with SMTP id f21-v6so3572839wmc.5 for ; Wed, 08 Aug 2018 10:41:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=opTec447AT1fFn8vy44X/EQsY/cudQgEF50iUF9hLGo=; b=Y0AwwGuPkcx3qaYflNRO9GzRrr5g4nDonm0JCQhyNaNU0vs7Jaw64ovE2+kIqossEM Oug1lsUO+56auh+5xJRUFBJk9Xa5oFYg/uo/BL6TjWZ8rUDTSDSZHRg0Rlh7R1HlQpuH t4QW7Ygir9Yvt0rjveTSng4BoQnN2/Rhc+dRnCF5TTvAFoJ85vA+cEfML7/quBmFsVk3 Oh9Kfjw6IFDo5XvhtkAPb09NMsHmZiiZT2GdCbNK6h0JYpovnslLSmB+mhmtcOiQliF9 BL1vX+QfyI+/fvK5tow8SEXzlRaaI9tsaZCfmXBYpRry11dcE1cw/el6YYxOukvolGGe otpg== MIME-Version: 1.0 Received: by 2002:adf:e44b:0:0:0:0:0 with HTTP; Wed, 8 Aug 2018 10:41:52 -0700 (PDT) In-Reply-To: <20180808124141.GK3155@embecosm.com> References: <20180808124141.GK3155@embecosm.com> From: Jim Wilson Date: Wed, 08 Aug 2018 17:41:00 -0000 Message-ID: Subject: Re: [PATCH 0/5] RISC-V Linux native port To: Andrew Burgess Cc: gdb-patches@sourceware.org Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-08/txt/msg00170.txt.bz2 On Wed, Aug 8, 2018 at 5:41 AM, Andrew Burgess wrote: > I think instructions on how to put together a working environment is > fine. I guess in this case access to actual hardware is probably > required so the number of people testing is going to be pretty low. > However, a link would be nice, so we can know we're all looking at the > same set of instructions. Where would I put those instructions? Jim