All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Uma Sharma <uma.sharma523@gmail.com>, Wei Liu <wei.liu2@citrix.com>
Cc: Ian.Jackson@citrix.com, Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [OPW PATCH V3] tools/xl: Call init function for libxl defined datatypes
Date: Mon, 20 Oct 2014 12:01:46 +0100	[thread overview]
Message-ID: <5444EB9A.9010509@eu.citrix.com> (raw)
In-Reply-To: <CALRCgArtnzRU77xh9=PZ75B0WFTAhUoK2E4P24vd8tONQ-BLnw@mail.gmail.com>

On 10/19/2014 02:15 PM, Uma Sharma wrote:
> Actually I looked at the patch sending documentation it stated that if
> some changes are already acknowledged then we have to write it.
> Should I write a new patch with all these changes ? Or I can make the
> changes in different patches?

"Acked-by: Wei Liu <...>" means, "Wei Liu has looked at everything in 
this patch and doesn't have any objections to it being committed."  That 
way, Ian J can just take a quick look and check it in, trusing Wei's 
judgement.

But in this case, Wei hasn't looked at the whole patch, but just half of 
it.  So Ian J might end up checking in code that hasn't been reviewed.

Usually, if you change the patch at all (apart from trivial things like 
whitespace or fixing clear violation of coding conventions) you have to 
drop the ack.

Since the code you're adding isn't necessarily connected to the code 
that was already acked, just making a separate patch would have been the 
best idea in this case.

  -George

  parent reply	other threads:[~2014-10-20 11:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-19 12:35 [OPW PATCH V3] tools/xl: Call init function for libxl defined datatypes Uma Sharma
2014-10-19 12:55 ` Wei Liu
2014-10-19 13:15   ` Uma Sharma
2014-10-19 13:47     ` Wei Liu
2014-10-20 11:01     ` George Dunlap [this message]
2014-10-20 11:29       ` Uma Sharma
2014-10-20 13:31         ` Ian Campbell
2014-10-20 13:36           ` Uma Sharma

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=5444EB9A.9010509@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=uma.sharma523@gmail.com \
    --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.