Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Dimitar Dimitrov <dimitar@dinux.eu>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: Re: [PATCH v6 1/3] PRU Simulator port
Date: Tue, 24 Sep 2019 04:45:00 -0000	[thread overview]
Message-ID: <7264472.ONEGvAOXSv@tpdeb> (raw)
In-Reply-To: <20190923211258.GK4962@embecosm.com>

On вторник, 24 септември 2019 г. 0:12:58 EEST Andrew Burgess wrote:
> From:	Andrew Burgess <andrew.burgess@embecosm.com>
> To:	Dimitar Dimitrov <dimitar@dinux.eu>
> CC:	gdb-patches@sourceware.org
> Sender:	gdb-patches-owner@sourceware.org
> List-Id:	<gdb-patches.sourceware.org>
> Date:	24.09.19 г. 0:12
> Spam Status:	Spamassassin 
> 
> * Dimitar Dimitrov <dimitar@dinux.eu> [2019-09-04 22:40:29 +0300]:
> > I'd like to contribute a sim port for the TI PRU I/O processor. This
> > is the sixth version of the patch series.
> > 
> > Changes since patch series v5:
> > - Added copyright headers to test cases.
> > - Regenerated using autoconf-2.69 and automake-1.5.1
> > - Added more comments to functions and MAC register enum.
> > - Updated copyright years.
> 
> Thanks for all this effort over the years!
> 
> I merged together patch #3 with #1 and pushed this to master.
> 
> Thanks,
> Andrew
Thank you for reviewing it.

Regards,
Dimitar




      reply	other threads:[~2019-09-24  4:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 19:41 Dimitar Dimitrov
2019-09-04 19:40 ` [PATCH v6 2/3] Add testsuite for the PRU simulator port Dimitar Dimitrov
2019-09-04 20:09 ` [PATCH v6 3/3] sim:pru: Autogenerated configure script Dimitar Dimitrov
2019-09-22  8:09 ` [PATCH v6 1/3] PRU Simulator port Dimitar Dimitrov
2019-09-23  8:59   ` Andrew Burgess
2019-09-23 21:13 ` Andrew Burgess
2019-09-24  4:45   ` Dimitar Dimitrov [this message]

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=7264472.ONEGvAOXSv@tpdeb \
    --to=dimitar@dinux.eu \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox