All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: JulienGrall <julien.grall@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v3 1/3] xen/string: Clean up {xen, arm}/string.h
Date: Mon, 15 May 2017 04:02:18 -0600	[thread overview]
Message-ID: <591998CA0200007800159BC6@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1494610552-8738-2-git-send-email-andrew.cooper3@citrix.com>

 >>> On 12.05.17 at 19:35, <andrew.cooper3@citrix.com> wrote:
> * Drop __kernel_size_t entirely.  It isn't useful distinction, especially as
>    it means the the prototypes don't appear to match their common definitions.
>  * Introduce __HAVE_ARCH_* guards for strpbrk(), strsep() and strspn(), which
>    match their implementation in common/string.c
>  * Apply consistent Xen style throughout.
> 
> No functional change.
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>

Reviewed-by: Jan Beulich <jbeulich@suse.com>



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

  reply	other threads:[~2017-05-15 10:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 17:35 [PATCH v3 for-next 0/3] Improvements to string.h Andrew Cooper
2017-05-12 17:35 ` [PATCH v3 1/3] xen/string: Clean up {xen, arm}/string.h Andrew Cooper
2017-05-15 10:02   ` Jan Beulich [this message]
2017-05-31  8:47   ` Julien Grall
2017-05-12 17:35 ` [PATCH v3 2/3] xen/string: Use compiler __builtin_*() where possible Andrew Cooper
2017-05-15 10:05   ` Jan Beulich
2017-05-12 17:35 ` [PATCH v3 3/3] x86/string: Clean up x86/string.h Andrew Cooper
2017-05-15 10:08   ` Jan Beulich
2017-05-15 10:19     ` Jan Beulich
2017-05-15 13:08       ` Andrew Cooper
2017-05-15 14:22         ` Jan Beulich
2017-05-31 12:42           ` Andrew Cooper
2017-05-31 13:00             ` Jan Beulich

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=591998CA0200007800159BC6@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --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.