linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: mingo@redhat.com, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH -resend 00/27] New macros for assembler symbols
Date: Mon, 14 May 2018 10:10:09 +0200	[thread overview]
Message-ID: <20180514081009.GC6607@gmail.com> (raw)
In-Reply-To: <20180510080644.19752-1-jslaby@suse.cz>


* Jiri Slaby <jslaby@suse.cz> wrote:

> This series introduces new macros for assembly as was discussed [1].
> The macros are introduced in the first patch of the series. The rest
> of patches start using these new macros in x86, converting *all* uses
> of the old macros to the new ones throughout the last patch. With
> every last user of some old macro, the macro is immediatelly made
> forbidden for x86.
> 
> When this settles down, conversion of other architectures can be done
> too.
> 
> For introduction, documentation, use and examples, please see
> Documentation/asm-annotations.rst from the first patch of the series.
> 
> [1] https://lkml.org/lkml/2017/3/1/742
> 
> Jiri Slaby (27):
>   linkage: new macros for assembler symbols
>   x86: assembly, use SYM_DATA for data
>   x86: assembly, annotate relocate_kernel
>   x86: entry, annotate THUNKs
>   x86: assembly, annotate local pseudo-functions
>   x86: crypto, annotate local functions
>   x86: boot, annotate local functions
>   x86: assembly, annotate aliases
>   x86: entry, annotate interrupt symbols properly
>   x86: head, annotate data appropriatelly
>   x86: boot, annotate data appropriatelly
>   x86: um, annotate data appropriatelly
>   x86: xen-pvh, annotate data appropriatelly
>   x86: purgatory, start using annotations
>   x86: assembly, do not annotate functions by GLOBAL
>   x86: assembly, use SYM_CODE_INNER_LABEL instead of GLOBAL
>   x86: realmode, use SYM_DATA_* instead of GLOBAL
>   x86: assembly, remove GLOBAL macro
>   x86: assembly, make some functions local
>   x86: ftrace, mark function_hook as function
>   x86_64: assembly, add ENDs to some functions and relabel with SYM_CODE_*
>   x86_64: assembly, change all ENTRY+END to SYM_CODE_*
>   x86_64: assembly, change all ENTRY+ENDPROC to SYM_FUNC_*
>   x86_32: assembly, add ENDs to some functions and relabel with SYM_CODE_*
>   x86_32: assembly, change all ENTRY+END to SYM_CODE_*
>   x86_32: assembly, change all ENTRY+ENDPROC to SYM_FUNC_*
>   x86: assembly, replace WEAK uses

So since this is going to be a lot of commits I'd rather not edit every title, but 
every single patch you sent has a non-standard title that looks totally out of 
place if you look at existing commits to those same files.

For example:

>   x86: boot, annotate local functions

Modifies files whose existing commit title format to be:

974f221c84b0: x86/boot: Move compressed kernel to the end of the decompression buffer
c04028813221: x86/boot: Clarify purpose of functions in misc.c

So could you please use the proper x86 titles?

In fact I'd suggest using the same subsystem identifier for most patches, i.e.:

   x86/asm: Annotate xen-pvh symbols ....

because these are really mostly assembly code annotations.

Thanks,

	Ingo

  parent reply	other threads:[~2018-05-14  8:10 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10  8:06 [PATCH -resend 00/27] New macros for assembler symbols Jiri Slaby
2018-05-10  8:06 ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 01/27] linkage: new " Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-14  3:04   ` Randy Dunlap
2018-05-14  3:04     ` Randy Dunlap
2018-05-14 12:54     ` Jiri Slaby
2018-05-14 12:54       ` Jiri Slaby
2018-05-14  8:03   ` Ingo Molnar
2018-05-14  8:03     ` Ingo Molnar
2018-05-10  8:06 ` [PATCH -resend 02/27] x86: assembly, use SYM_DATA for data Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-14  8:05   ` Ingo Molnar
2018-05-14  8:05     ` Ingo Molnar
2018-05-15  6:39     ` Ingo Molnar
2018-05-15  6:39       ` Ingo Molnar
2018-05-18  9:17       ` Jiri Slaby
2018-05-18  9:17         ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 03/27] x86: assembly, annotate relocate_kernel Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 04/27] x86: entry, annotate THUNKs Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 05/27] x86: assembly, annotate local pseudo-functions Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 06/27] x86: crypto, annotate local functions Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 07/27] x86: boot, " Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 08/27] x86: assembly, annotate aliases Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 09/27] x86: entry, annotate interrupt symbols properly Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 10/27] x86: head, annotate data appropriatelly Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 11/27] x86: boot, " Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 12/27] x86: um, " Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 13/27] x86: xen-pvh, " Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 14/27] x86: purgatory, start using annotations Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 15/27] x86: assembly, do not annotate functions by GLOBAL Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 16/27] x86: assembly, use SYM_CODE_INNER_LABEL instead of GLOBAL Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 17/27] x86: realmode, use SYM_DATA_* " Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 18/27] x86: assembly, remove GLOBAL macro Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 19/27] x86: assembly, make some functions local Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 20/27] x86: ftrace, mark function_hook as function Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 21/27] x86_64: assembly, add ENDs to some functions and relabel with SYM_CODE_* Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 22/27] x86_64: assembly, change all ENTRY+END to SYM_CODE_* Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 23/27] x86_64: assembly, change all ENTRY+ENDPROC to SYM_FUNC_* Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 24/27] x86_32: assembly, add ENDs to some functions and relabel with SYM_CODE_* Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 25/27] x86_32: assembly, change all ENTRY+END to SYM_CODE_* Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 26/27] x86_32: assembly, change all ENTRY+ENDPROC to SYM_FUNC_* Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-10  8:06 ` [PATCH -resend 27/27] x86: assembly, replace WEAK uses Jiri Slaby
2018-05-10  8:06   ` Jiri Slaby
2018-05-14  8:10 ` Ingo Molnar [this message]
2018-05-14  8:10   ` [PATCH -resend 00/27] New macros for assembler symbols 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=20180514081009.GC6607@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=jslaby@suse.cz \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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).