All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Continue OpenRISC contibution
Date: Fri, 27 Aug 2021 08:41:47 +0900	[thread overview]
Message-ID: <YSgmu/bnzRnI7AGI@antec> (raw)
In-Reply-To: <CADGJwMwapL_eB_ZqKmaDsoFxCY_3qvKu=0BfdSGQZaC5GEjP1Q@mail.gmail.com>

On Thu, Aug 26, 2021 at 10:17:17PM +0530, Harshitha S wrote:
> Hello,
> 
> I'm thinking of continuing my contribution to the OpenRISC project. With my
> GSoC project, I have learned too many new skills and wish to keep this
> learning pace. I would be happy to learn and explore new skills. Please let
> me know what I can work upon.

Hi Harshita,

(CCing list)

Glad to hear you are still interested.  I think there are always plenty of
things, some things on the top of my head:
  - Simple - update the mor1kx/readme.md to explain we support formal
  - Medium - fix the bugs that you raised
  - Bigger - or1k-formal (like riscv-formal, formally verify each instruction)

-Stafford

       reply	other threads:[~2021-08-26 23:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADGJwMwapL_eB_ZqKmaDsoFxCY_3qvKu=0BfdSGQZaC5GEjP1Q@mail.gmail.com>
2021-08-26 23:41 ` Stafford Horne [this message]
2021-08-28 17:17   ` [OpenRISC] Continue OpenRISC contibution Harshitha S
2021-08-31 13:47     ` Stafford Horne
2021-08-31 14:02       ` Harshitha S
2021-08-31 15:30       ` Dan
2021-08-31 16:53         ` Harshitha S
2021-08-31 17:07           ` Dan
2021-08-31 17:08           ` Dan
2021-08-31 18:22             ` Harshitha S
2021-09-01 13:26     ` Stafford Horne
     [not found]       ` <CADGJwMzCa_u2+V3Tu-pp92GgxubwiU0HQo0Dy5G3b0sAO2xzFw@mail.gmail.com>
2021-09-01 21:06         ` Stafford Horne
     [not found]           ` <CADGJwMxxEp4YFTe4271LJHoc4sJo2P6mtNOFhx+w6+phF25xDQ@mail.gmail.com>
2021-09-02 12:02             ` Stafford Horne

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=YSgmu/bnzRnI7AGI@antec \
    --to=shorne@gmail.com \
    --cc=openrisc@lists.librecores.org \
    /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.