From: Jan Beulich <jbeulich@suse.com> To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org> Cc: Andrew Cooper <andrew.cooper3@citrix.com>, George Dunlap <george.dunlap@citrix.com>, Ian Jackson <iwj@xenproject.org>, Julien Grall <julien@xen.org>, Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org> Subject: [PATCH v2 00/20] further population of xen/lib/ Date: Wed, 21 Apr 2021 16:15:48 +0200 [thread overview] Message-ID: <3ae091ce-6f6c-3ec6-abd3-4490239a707f@suse.com> (raw) This is to dissolve / move xen/common/string.c. One benefit of moving these functions into an archive is that we can drop some of the related __HAVE_ARCH_* #define-s: By living in an archive, the per-arch functions will preempt any loading of the respective functions (objects) from the archive. (Down the road we may want to move the per-arch functions into archives as well, at which point the per-arch archive(s) would need to be specified ahead of the common one(s) to the linker.) The only change in v2 is adjustment to all of the commit messages. 01: lib: move memset() 02: lib: move memcpy() 03: lib: move memmove() 04: lib: move memcmp() 05: lib: move memchr() 06: lib: move memchr_inv() 07: lib: move strlen() 08: lib: move strnlen() 09: lib: move strcmp() 10: lib: move strncmp() 11: lib: move strlcpy() 12: lib: move strlcat() 13: lib: move strchr() 14: lib: move strrchr() 15: lib: move strstr() 16: lib: move strcasecmp() 17: lib: move/rename strnicmp() to strncasecmp() 18: lib: move strspn() 19: lib: move strpbrk() 20: lib: move strsep() Jan
next reply other threads:[~2021-04-21 14:16 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-21 14:15 Jan Beulich [this message] 2021-04-21 14:18 ` [PATCH v2 01/20] lib: move memset() Jan Beulich 2021-04-21 14:18 ` [PATCH v2 02/20] lib: move memcpy() Jan Beulich 2021-04-21 14:19 ` [PATCH v2 03/20] lib: move memmove() Jan Beulich 2021-04-21 14:19 ` [PATCH v2 04/20] lib: move memcmp() Jan Beulich 2021-04-21 14:20 ` [PATCH v2 05/20] lib: move memchr() Jan Beulich 2021-04-21 14:20 ` [PATCH v2 06/20] lib: move memchr_inv() Jan Beulich 2021-04-21 14:22 ` [PATCH v2 07/20] lib: move strlen() Jan Beulich 2021-04-21 14:22 ` [PATCH v2 08/20] lib: move strnlen() Jan Beulich 2021-04-21 14:22 ` [PATCH v2 09/20] lib: move strcmp() Jan Beulich 2021-04-21 14:23 ` [PATCH v2 10/20] lib: move strncmp() Jan Beulich 2021-04-21 14:23 ` [PATCH v2 11/20] lib: move strlcpy() Jan Beulich 2021-04-21 14:24 ` [PATCH v2 12/20] lib: move strlcat() Jan Beulich 2021-04-21 14:24 ` [PATCH v2 13/20] lib: move strchr() Jan Beulich 2021-04-21 14:24 ` [PATCH v2 14/20] lib: move strrchr() Jan Beulich 2021-04-21 14:25 ` [PATCH v2 15/20] lib: move strstr() Jan Beulich 2021-04-21 14:25 ` [PATCH v2 16/20] lib: move strcasecmp() Jan Beulich 2021-04-21 14:25 ` [PATCH v2 17/20] lib: move/rename strnicmp() to strncasecmp() Jan Beulich 2021-04-21 19:20 ` Julien Grall 2021-04-21 14:26 ` [PATCH v2 18/20] lib: move strspn() Jan Beulich 2021-04-21 14:26 ` [PATCH v2 19/20] lib: move strpbrk() Jan Beulich 2021-04-21 14:26 ` [PATCH v2 20/20] lib: move strsep() Jan Beulich 2021-04-21 19:21 ` [PATCH v2 00/20] further population of xen/lib/ Julien Grall
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=3ae091ce-6f6c-3ec6-abd3-4490239a707f@suse.com \ --to=jbeulich@suse.com \ --cc=andrew.cooper3@citrix.com \ --cc=george.dunlap@citrix.com \ --cc=iwj@xenproject.org \ --cc=julien@xen.org \ --cc=sstabellini@kernel.org \ --cc=wl@xen.org \ --cc=xen-devel@lists.xenproject.org \ --subject='Re: [PATCH v2 00/20] further population of xen/lib/' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).