From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>, xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Anshul Makkar <anshul.makkar@citrix.com>,
Meng Xu <mengxu@cis.upenn.edu>
Subject: Re: [PATCH] xen: sched: improve debug dump output.
Date: Thu, 2 Feb 2017 17:59:00 +0100 [thread overview]
Message-ID: <1486054740.18830.72.camel@citrix.com> (raw)
In-Reply-To: <2d136d04-5afb-ae77-e556-bdfeb49b2dc0@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1833 bytes --]
On Wed, 2017-02-01 at 14:59 +0000, George Dunlap wrote:
> On 26/01/17 16:52, Dario Faggioli wrote:
> >
> > Scheduling information debug dump for Credit2 is hard
> > to read as it contains the same information repeated
> > multiple time in different ways.
> >
> > [..]
> >
> > Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
>
> Hang on -- how does this relate to the credit2 dumping patch you sent
> the previous week?
>
Err... Right, I'll tell you how they're related: I basically forgot
that I did send the earlier one! :-(
> I'm all in favor of not saving up a massive queue of patches, but if
> the
> patches have conflicts with existing patches, I think it would be
> better
> if you re-sent a full series with a new version number, so I wouldn't
> have to try to figure out what order they needed to be applied in and
> which ones weren't necessary anymore. There's no problem, I don't
> think, of sending version n+1 of a series that has no changes other
> than
> adding new patches.
>
Indeed. But the problem in this case is I lost track of the fact that I
did send the other one, and so I resent, after reworking it a bit more.
Sorry for the confusion, this is totally my fault. :-/
> I've checked in and pushed the three patches that I reviewed today;
> can
> you rebase your outstanding changes and send another series?
>
Ok, I'll rebase this one on top of current staging and resubmit.
> Thanks! And sorry it took so long to get to.
>
Well, sorry for the mess. :-P
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-02-02 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 16:52 [PATCH] xen: sched: improve debug dump output Dario Faggioli
2017-01-26 18:59 ` Meng Xu
2017-01-26 22:08 ` Dario Faggioli
2017-01-27 17:05 ` Meng Xu
2017-01-27 18:36 ` Dario Faggioli
2017-01-27 19:26 ` Meng Xu
2017-01-27 19:28 ` Meng Xu
2017-02-01 14:59 ` George Dunlap
2017-02-02 16:59 ` Dario Faggioli [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=1486054740.18830.72.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=anshul.makkar@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=mengxu@cis.upenn.edu \
--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.