qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Chris Wulff <crwulff@gmail.com>, Marek Vasut <marex@denx.de>
Subject: Re: [Qemu-devel] [PATCH v7 2/2] Add Nios II semihosting support.
Date: Thu, 4 Apr 2019 14:18:08 +0700	[thread overview]
Message-ID: <CAFEAcA8g0qQadBjiOU9P_BRNiXJx0WPp11Y0qRmoO-jGDbMteA@mail.gmail.com> (raw)
In-Reply-To: <5a4d38da-3ccc-b019-3f30-54cd364f7544@codesourcery.com>

On Thu, 4 Apr 2019 at 14:13, Sandra Loosemore <sandra@codesourcery.com> wrote:
>
> On 4/4/19 1:00 AM, Peter Maydell wrote:
> > On Thu, 4 Apr 2019 at 13:44, Sandra Loosemore <sandra@codesourcery.com> wrote:
> >>
> >> On 4/3/19 11:59 PM, Peter Maydell wrote:
> >>> On Thu, 4 Apr 2019 at 02:53, Sandra Loosemore <sandra@codesourcery.com> wrote:
> >>>>
> >>>> This patch adds support for libgloss semihosting to Nios II bare-metal
> >>>> emulation.  The specification for the protocol can be found in the
> >>>> libgloss sources.
> >>>>
> >>>> Signed-off-by: Sandra Loosemore <sandra@codesourcery.com>
> >>>> Signed-off-by: Julian Brown <julian@codesourcery.com>
> >>>
> >>> I gave a reviewed-by tag for this patch in v6 -- has something changed
> >>> in v7 that made that no longer able to carry across?
> >>
> >> I fixed the formatting problems you asked me to address.  What else am I
> >> supposed to do?  I don't understand what you mean about the tag.
> >
> > If somebody provides you with a Reviewed-by tag and you submit
> > a fresh version of the patchset then you should include that tag in
> > your commit message; that records that the patch has been reviewed
> > so that people know it doesn't need to be looked at again.
> > https://wiki.qemu.org/Contribute/SubmitAPatch#Proper_use_of_Reviewed-by:_tags_can_aid_review
>
> Hmmm, OK; I missed that.  So do I need to resubmit the patches just to
> add that tag?

No, not at this point. I'll just add one here:
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>

which should cause the automated tooling to pick it up when
it gets applied to somebody's tree for a pullreq.

thanks
-- PMM

  reply	other threads:[~2019-04-04  7:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 19:53 [Qemu-devel] [PATCH v7 0/2] Nios II generic board config and semihosting Sandra Loosemore
2019-04-03 19:53 ` [Qemu-devel] [PATCH v7 1/2] Add generic Nios II board Sandra Loosemore
2019-04-29 12:38   ` Peter Maydell
2019-04-29 12:38     ` Peter Maydell
2019-04-03 19:53 ` [Qemu-devel] [PATCH v7 2/2] Add Nios II semihosting support Sandra Loosemore
2019-04-04  5:59   ` Peter Maydell
2019-04-04  6:44     ` Sandra Loosemore
2019-04-04  7:00       ` Peter Maydell
2019-04-04  7:13         ` Sandra Loosemore
2019-04-04  7:18           ` Peter Maydell [this message]
2019-04-29 15:55 ` [Qemu-devel] [PATCH v7 0/2] Nios II generic board config and semihosting Peter Maydell
2019-04-29 15:55   ` Peter Maydell
2019-04-29 16:02   ` Sandra Loosemore
2019-04-29 16:02     ` Sandra Loosemore

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=CAFEAcA8g0qQadBjiOU9P_BRNiXJx0WPp11Y0qRmoO-jGDbMteA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=crwulff@gmail.com \
    --cc=marex@denx.de \
    --cc=qemu-devel@nongnu.org \
    --cc=sandra@codesourcery.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).