All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Alexandra Sandulescu <alexandra.sandulescu1@1and1.ro>,
	Alexandra Sandulescu <alecsandra.sandulescu@gmail.com>
Subject: Re: [OPW PATCH V3] tools: xl: refactor code to parse network device options
Date: Tue, 21 Oct 2014 16:29:46 +0100	[thread overview]
Message-ID: <1413905386.23337.53.camel@citrix.com> (raw)
In-Reply-To: <20141021152420.GI10234@zion.uk.xensource.com>

On Tue, 2014-10-21 at 16:24 +0100, Wei Liu wrote:
> Now we are in freeze, not sure how applicable is it for this patch to go
> in.
> 
> To Konrad:
> 
> -ve: this is only code refactoring, not bug fix
> +ve: the risk of introducing bug is low as 1) this refactoring is
>      straight-forward, 2) the code path is tested in OSSTest.

Note that this was a task I suggested as part of the OPW application
process. I said to Alexandra at the time:
        
        I think OPW wants you to get a patch accepted as part of the application
        process, however Xen is currently in code freeze for the 4.5 release so
        I think we will have to aim for a patch in a state where it could/would
        be accepted if there was no code freeze. The patch can then be held
        until the 4.6 development cycle opens and be applied then.

Of course if the patch was allowed in now that would be awesome too ;-)

Ian.

  reply	other threads:[~2014-10-21 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 14:19 [OPW PATCH V3] tools: xl: refactor code to parse network device options Alexandra Sandulescu
2014-10-21 14:22 ` Alexandra Sandulescu
2014-10-21 15:24 ` Wei Liu
2014-10-21 15:29   ` Ian Campbell [this message]
2014-10-21 16:27 ` Konrad Rzeszutek Wilk

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=1413905386.23337.53.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=alecsandra.sandulescu@gmail.com \
    --cc=alexandra.sandulescu1@1and1.ro \
    --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.