From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] tools/gdbsx: fix 'g' packet response for 64bit guests
Date: Tue, 31 Jul 2018 18:04:56 +0200 [thread overview]
Message-ID: <20180731160456.GQ1371@mail-itl> (raw)
In-Reply-To: <5B60176302000078001D941A@prv1-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 601 bytes --]
On Tue, Jul 31, 2018 at 02:01:39AM -0600, Jan Beulich wrote:
> >>> On 31.07.18 at 04:30, <marmarek@invisiblethingslab.com> wrote:
>
> Marek,
>
> looks like all of the patches you've sent early this morning local time
> here came through twice on xen-devel: Would you please avoid
> having xen-devel on both the To and the Cc lists (just with different
> domains)?
Sorry about that, now fixed my setup.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-07-31 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 2:30 [PATCH] tools/gdbsx: fix 'g' packet response for 64bit guests Marek Marczykowski-Górecki
2018-07-31 8:01 ` Jan Beulich
2018-07-31 8:09 ` Andrew Cooper
2018-07-31 8:35 ` Jan Beulich
2018-07-31 16:04 ` Marek Marczykowski [this message]
2018-07-31 9:00 ` Wei Liu
2018-07-31 9:08 ` Andrew Cooper
2018-07-31 9:12 ` Wei Liu
2018-07-31 16:10 ` Marek Marczykowski-Górecki
2018-07-31 16:28 ` Wei Liu
2018-07-31 16:29 ` Andrew Cooper
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=20180731160456.GQ1371@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=elena.ufimtseva@oracle.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.