From: Dario Faggioli <raistlin@linux.it>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Keir (Xen.org)" <keir@xen.org>
Subject: Re: [PATCH 0 of 1] sched: rework locking for dump debugkey.
Date: Wed, 18 Jan 2012 17:28:10 +0100 [thread overview]
Message-ID: <1326904090.5856.38.camel@Solace> (raw)
In-Reply-To: <4F16FFC5020000780006D81B@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 843 bytes --]
On Wed, 2012-01-18 at 16:22 +0000, Jan Beulich wrote:
> > I think this patch correctly deals with locking in this specific case,
> > but of course I'm happy to hear what you think! :-)
>
> Forgot to include/attach the patch?
>
No, it's coming but you're right, my "submission machinery" definitely
need some refinements! :-)
Will do that ASAP, as I expect to start submitting more complex series
in the coming period, and this method I'm using now does not scale.
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-------------------------------------------------------------------
Dario Faggioli, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
PhD Candidate, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-01-18 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 16:13 [PATCH 0 of 1] sched: rework locking for dump debugkey Dario Faggioli
2012-01-18 16:22 ` Jan Beulich
2012-01-18 16:28 ` Dario Faggioli [this message]
2012-01-18 16:24 ` [PATCH 1 " Dario Faggioli
2012-01-26 16:37 ` George Dunlap
2012-01-26 16:55 ` Dario Faggioli
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=1326904090.5856.38.camel@Solace \
--to=raistlin@linux.it \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.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 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.