All of lore.kernel.org
 help / color / mirror / Atom feed
From: Praveen Kumar <kpraveen.lkml@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: tim@xen.org, sstabellini@kernel.org, wei.liu2@citrix.com,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v5 01/17] rbtree: changes to align the coding conventions with Linux tree
Date: Fri, 4 Aug 2017 22:51:54 +0530	[thread overview]
Message-ID: <CABcWhv5V5EAuHUfbjJE8FhJCnp5m0bxe-Rg4av9NtnRdS=cjCA@mail.gmail.com> (raw)
In-Reply-To: <5984A933020000780010368F@prv-mh.provo.novell.com>

I tried applying the patches generated from Linux tree and updating
the file location ( as per the Xen tree location ); some of the
places, I was facing issues.
Adding comment to the file, resolved some of the patching issues. So,
this is my understanding ( could be completely wrong ) that, with the
change in location and difference in code statements, the patch
application have failed. Please suggest if I can perform this is a
better way. Thanks in advance.

On Fri, Aug 4, 2017 at 10:34 PM, Jan Beulich <jbeulich@suse.com> wrote:
>>>> Praveen Kumar <kpraveen.lkml@gmail.com> 08/04/17 7:00 PM >>>
>>There will be issue while directly applying the patch from Linux tree
>>( having changed the file name ) as the line number changes.
>
> How do line numbers matter?
>
> Jan
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-08-04 17:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14  8:26 [PATCH v5 00/17] xen: common: rbtree: ported updates from Linux tree Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 01/17] rbtree: changes to align the coding conventions with " Praveen Kumar
2017-07-14 12:28   ` Jan Beulich
2017-07-14 12:51     ` Praveen Kumar
2017-07-14 13:05       ` Jan Beulich
2017-08-03 10:37         ` Dario Faggioli
2017-08-04 16:59           ` Praveen Kumar
2017-08-04 17:04             ` Jan Beulich
2017-08-04 17:21               ` Praveen Kumar [this message]
2017-08-06  7:42                 ` Jan Beulich
2017-07-14  8:26 ` [PATCH v5 02/17] rbtree: remove redundant if()-condition in rb_erase() Praveen Kumar
2017-08-03 10:11   ` Jan Beulich
2017-07-14  8:26 ` [PATCH v5 03/17] rbtree: empty nodes have no color Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 04/17] rbtree: move some implementation details from rbtree.h to rbtree.c Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 05/17] rbtree: break out of rb_insert_color loop after tree rotation Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 06/17] rbtree: adjust root color in rb_insert_color() only when necessary Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 07/17] rbtree: low level optimizations in rb_insert_color() Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 08/17] rbtree: adjust node color in __rb_erase_color() only when necessary Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 09/17] rbtree: optimize case selection logic in __rb_erase_color() Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 10/17] rbtree: low level optimizations " Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 11/17] rbtree: coding style adjustments Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 12/17] rbtree: optimize fetching of sibling node Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 13/17] rbtree: add __rb_change_child() helper function Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 14/17] rbtree: place easiest case first in rb_erase() Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 15/17] rbtree: handle 1-child recoloring in rb_erase() instead of rb_erase_color() Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 16/17] rbtree: low level optimizations in rb_erase() Praveen Kumar
2017-07-14  8:26 ` [PATCH v5 17/17] rbtree: fix typo in comment of rb_insert_color Praveen Kumar

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='CABcWhv5V5EAuHUfbjJE8FhJCnp5m0bxe-Rg4av9NtnRdS=cjCA@mail.gmail.com' \
    --to=kpraveen.lkml@gmail.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=sstabellini@kernel.org \
    --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.