From: Fredrik Noring <noring@nocrew.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Stefan Markovic" <smarkovic@wavecomp.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Aleksandar Rikalo" <arikalo@wavecomp.com>,
"Emilio G. Cota" <cota@braap.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
"Jürgen Urban" <JuergenUrban@gmx.de>,
"Petar Jovanovic" <pjovanovic@wavecomp.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] Correction needed for R5900 instruction decoding
Date: Fri, 2 Nov 2018 16:49:23 +0100 [thread overview]
Message-ID: <20181102154923.GB2274@sx9> (raw)
In-Reply-To: <CAFEAcA9KJn++ASQ+xzEAs+pi0xkZG7i3aPUZEQZXwRfYJy6jbw@mail.gmail.com>
Hi Peter,
> From the other side of things, as a submaintainer around release
> time there's often a lot of work to do and it's easy to confuse
> different patchsets or forget the status of them, so it's useful
> to have a patch series which is exactly the set of patches that
> the submitter thinks are suitable to go into the release, and it's
> less work to apply those than to fish out a subset of patches
> from a series.
Understood. Aleksandar previously indicated that he wanted an amendment
series with changes ordered by importance, which is why the two patches
were part of that series (as the first ones).
> So overall, I think my suggestion would be that the best move
> from here would be for Fred to send a patchset with the changes
> for 3.1 and only those changes. Could you do that, please?
Yes, I will post a separate series for review immediately.
Fredrik
next prev parent reply other threads:[~2018-11-02 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 11:06 [Qemu-devel] Correction needed for R5900 instruction decoding Aleksandar Markovic
2018-11-01 14:31 ` Philippe Mathieu-Daudé
2018-11-01 17:23 ` Fredrik Noring
2018-11-01 18:07 ` Aleksandar Markovic
2018-11-02 13:43 ` Aleksandar Markovic
2018-11-02 14:31 ` Fredrik Noring
2018-11-02 15:03 ` Aleksandar Markovic
2018-11-02 15:18 ` Peter Maydell
2018-11-02 15:49 ` Fredrik Noring [this message]
2018-11-01 14:35 ` Emilio G. Cota
2018-11-02 17:51 ` Philippe Mathieu-Daudé
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=20181102154923.GB2274@sx9 \
--to=noring@nocrew.org \
--cc=JuergenUrban@gmx.de \
--cc=amarkovic@wavecomp.com \
--cc=arikalo@wavecomp.com \
--cc=cota@braap.org \
--cc=macro@linux-mips.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=pjovanovic@wavecomp.com \
--cc=qemu-devel@nongnu.org \
--cc=smarkovic@wavecomp.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).