From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"open list:bochs" <qemu-block@nongnu.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Max Reitz" <mreitz@redhat.com>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Aleksandar Rikalo" <aleksandar.rikalo@rt-rk.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [PULL for-4.2-rc2 0/2] Tracing patches
Date: Tue, 19 Nov 2019 22:14:24 +0100 [thread overview]
Message-ID: <CAL1e-=ibQBWUzUZvsvSWCZ5SwFk5T+b2P94D068W8G_taWVASg@mail.gmail.com> (raw)
In-Reply-To: <20191119204551.240792-1-stefanha@redhat.com>
On Tue, Nov 19, 2019 at 9:46 PM Stefan Hajnoczi <stefanha@redhat.com> wrote:
>
> The following changes since commit f086f22d6c068ba151b0f6e81e75a64f130df712:
>
> Merge remote-tracking branch 'remotes/awilliam/tags/vfio-fixes-20191118.0' into staging (2019-11-18 21:35:48 +0000)
>
> are available in the Git repository at:
>
> https://github.com/stefanha/qemu.git tags/tracing-pull-request
>
> for you to fetch changes up to 6b904f1a528a6d8c21f7fbdeab13b9603d1b6df7:
>
> hw/mips/gt64xxx: Remove dynamic field width from trace events (2019-11-19 16:17:05 +0000)
>
> ----------------------------------------------------------------
> Pull request
>
> Tracing fixes for MIPS.
>
> ----------------------------------------------------------------
>
Hello, Stefan, Philippe, Peter.
This appears to be a duplicate of the pull request sent today by Philippe
(and already applied by Peter just hours ago):
https://lists.gnu.org/archive/html/qemu-devel/2019-11/msg02894.html
The patches from the two pull requests appear to be identical, except
some minor details in commit messages: Stefan's versions contain
"Message-Id:" identifiers, while Philippe's don't (my suggestion to
Philippe is to include "Message-Id:" for all patches that are part of any
pull request in future; this can be achieved effortlessly/automatically
by applying patches using patchwork).
In summary, for this very situation, it looks to me we are all set, no need
for Peter to process this pull request.
Regards,
Aleksandar
> Philippe Mathieu-Daudé (2):
> hw/block/pflash: Remove dynamic field width from trace events
> hw/mips/gt64xxx: Remove dynamic field width from trace events
>
> hw/block/pflash_cfi01.c | 8 ++++----
> hw/block/pflash_cfi02.c | 8 ++++----
> hw/block/trace-events | 8 ++++----
> hw/mips/gt64xxx_pci.c | 16 ++++++++--------
> hw/mips/trace-events | 4 ++--
> 5 files changed, 22 insertions(+), 22 deletions(-)
>
> --
> 2.23.0
>
>
next prev parent reply other threads:[~2019-11-19 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 20:45 [PULL for-4.2-rc2 0/2] Tracing patches Stefan Hajnoczi
2019-11-19 20:45 ` [PULL for-4.2-rc2 1/2] hw/block/pflash: Remove dynamic field width from trace events Stefan Hajnoczi
2019-11-19 20:45 ` [PULL for-4.2-rc2 2/2] hw/mips/gt64xxx: " Stefan Hajnoczi
2019-11-19 21:14 ` Aleksandar Markovic [this message]
2019-11-19 21:35 ` [PULL for-4.2-rc2 0/2] Tracing patches Aleksandar Markovic
2019-11-20 9:33 ` Philippe Mathieu-Daudé
2019-11-20 10:41 ` Stefan Hajnoczi
2019-11-20 9:19 ` Philippe Mathieu-Daudé
2019-11-20 5:39 ` no-reply
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='CAL1e-=ibQBWUzUZvsvSWCZ5SwFk5T+b2P94D068W8G_taWVASg@mail.gmail.com' \
--to=aleksandar.m.mail@gmail.com \
--cc=aleksandar.rikalo@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).