All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Keir Fraser <keir.xen@gmail.com>
Subject: Re: Spurious Acks (was Re: PVH domU patches....)
Date: Thu, 8 Aug 2013 08:57:56 -0400	[thread overview]
Message-ID: <20130808125756.GA3885@konrad-lan.dumpdata.com> (raw)
In-Reply-To: <520363B602000078000EA1FD@nat28.tlf.novell.com>

On Thu, Aug 08, 2013 at 08:24:06AM +0100, Jan Beulich wrote:
> >>> On 08.08.13 at 02:46, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > Maybe we should copy the SubmittingPatches from Linux in the file so we
> > have it in there and just base it on that?
> 
> Our flow is a bit different from theirs, so doing so without some
> editing might cause more confusion than clarification.

Sounds a like a perfect candidate then - otherwise we are bound to hit
issues when folks are used to Linux try to develop in Xen and hit the
process problem.

I will post a patch with the initial copy of SubmittingPatches and then
some on follow patches with some modifications of what I think had been
discussed in the past.

> 
> Jan
> 

      reply	other threads:[~2013-08-08 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01 10:21 Spurious Acks (was Re: PVH domU patches....) Tim Deegan
2013-08-05 21:18 ` Mukesh Rathor
2013-08-06 10:00   ` George Dunlap
2013-08-06 10:10     ` Ian Campbell
2013-08-06 13:00     ` Konrad Rzeszutek Wilk
2013-08-06 13:38       ` Tim Deegan
2013-08-06 13:43       ` Wei Liu
2013-08-08  0:46         ` Konrad Rzeszutek Wilk
2013-08-08  7:24           ` Jan Beulich
2013-08-08 12:57             ` Konrad Rzeszutek Wilk [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=20130808125756.GA3885@konrad-lan.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=keir.xen@gmail.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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.