From: Jiri Slaby <jslaby@suse.cz>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Juergen Gross <jgross@suse.com>,
linux-pm@vger.kernel.org, x86@kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
Pavel Machek <pavel@ucw.cz>,
hpa@zytor.com, xen-devel@lists.xenproject.org,
tglx@linutronix.de, Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v2 03/10] x86: assembly, use SYM_FUNC_END for functions
Date: Wed, 22 Mar 2017 16:44:52 +0100 [thread overview]
Message-ID: <e4f7197c-559e-0dc2-c4e4-e369bf503cbb@suse.cz> (raw)
In-Reply-To: <20170322142610.bo5c6wzlbqnxrgt3@treble>
On 03/22/2017, 03:26 PM, Josh Poimboeuf wrote:
> On Mon, Mar 20, 2017 at 01:32:15PM +0100, Jiri Slaby wrote:
>> Somewhere END was used to end a function, elsewhere, nothing was used.
>> So unify it and mark them all by SYM_FUNC_END.
>>
>> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
>
> For me these patches would be easier to review if the SYM_FUNC_START and
> SYM_FUNC_END pairs for a given function are done in the same patch.
This patchset was intended to make everything paired with minimum
changes. I certainly can change also counter-elements of each
added/changed one if you prefer.
> Also I noticed several cases in entry_64.S where the old ENTRY macro is
> still used, and paired with SYM_FUNC_END.
>
> Maybe there should be an x86 version of the deprecated ENTRY/ENDPROC/etc
> macros which throw a warning or an error?
Yes, my plan is to throw ENTRY/ENDPROC on the floor from x86 completely.
And I will do it after this patchset settles down by sed or something in
one shot (per directory or something).
thanks,
--
js
suse labs
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-22 15:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9ea5e137-61f9-dccc-bb9d-ac3ff86e5867@suse.cz>
2017-03-20 12:32 ` [PATCH v2 01/10] linkage: new macros for assembler symbols Jiri Slaby
[not found] ` <20170320123222.15453-1-jslaby@suse.cz>
2017-03-20 12:32 ` [PATCH v2 02/10] x86: assembly, FUNC_START for fn, DATA_START for data Jiri Slaby
2017-03-20 13:32 ` Josh Poimboeuf
2017-03-20 15:32 ` Jiri Slaby
2017-03-20 16:07 ` Josh Poimboeuf
2017-03-21 14:08 ` Pavel Machek
2017-03-22 7:25 ` Ingo Molnar
[not found] ` <20170322072557.GA13904@gmail.com>
2017-03-22 7:39 ` Jiri Slaby
[not found] ` <ee3242f9-1fab-f3a8-947d-85fc1a660a49@suse.cz>
2017-03-22 7:46 ` Ingo Molnar
[not found] ` <20170322074616.GA10809@gmail.com>
2017-03-22 14:11 ` Josh Poimboeuf
[not found] ` <20170322141123.opss3u4gpupqgl2q@treble>
2017-03-22 15:01 ` Jiri Slaby
[not found] ` <049e6c03-8d7d-e869-96bd-0a98e6471227@suse.cz>
2017-03-22 15:33 ` Josh Poimboeuf
2017-03-23 7:38 ` Ingo Molnar
[not found] ` <20170323073819.GA14258@gmail.com>
2017-03-23 13:24 ` Josh Poimboeuf
2017-03-22 12:06 ` Jiri Slaby
[not found] ` <fd0cb783-b07f-f636-04a8-d8a115de1a17@suse.cz>
2017-03-22 15:52 ` Pavel Machek
2017-03-20 12:32 ` [PATCH v2 03/10] x86: assembly, use SYM_FUNC_END for functions Jiri Slaby
2017-03-20 12:32 ` [PATCH v2 07/10] x86: assembly, annotate aliases Jiri Slaby
[not found] ` <20170320123222.15453-3-jslaby@suse.cz>
2017-03-21 14:48 ` [PATCH v2 03/10] x86: assembly, use SYM_FUNC_END for functions Josh Poimboeuf
[not found] ` <20170321144841.oeaqqarhgzyhehth@treble>
2017-03-22 7:29 ` Ingo Molnar
2017-03-22 14:26 ` Josh Poimboeuf
[not found] ` <20170322142610.bo5c6wzlbqnxrgt3@treble>
2017-03-22 15:44 ` Jiri Slaby [this message]
2017-04-10 11:23 ` Jiri Slaby
[not found] ` <b7800998-2a60-b967-10fc-482ebd6fadf0@suse.cz>
2017-04-10 19:35 ` Josh Poimboeuf
[not found] ` <20170410193512.d67vefxedoockybg@treble>
2017-04-12 6:24 ` Jiri Slaby
[not found] ` <e79c90da-6785-e888-2f77-a5f2083698e0@suse.cz>
2017-04-12 6:52 ` Ingo Molnar
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=e4f7197c-559e-0dc2-c4e4-e369bf503cbb@suse.cz \
--to=jslaby@suse.cz \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--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 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).