Messages in this thread | | | From | Nick Desaulniers <> | Date | Mon, 22 Jul 2019 14:41:21 -0700 | Subject | Re: [PATCH v2 0/2] Support kexec/kdump for clang built kernel |
| |
Joe, Is it possible to have scripts/get_maintainer.pl always cc linux-kernel@vger.kernel.org? I just sent out a series, and it seems the cover letter didn't get sent to LKML. I usually use this shell function to send patches: ``` function kpatch () { patch=$1 shift git send-email \ --cc-cmd="./scripts/get_maintainer.pl --norolestats $patch" \ $@ $patch } ```
Invoked via: ``` $ mkdir purgatory $ git format-patch HEAD~2 --cover-letter -o purgatory -v2 $ kpatch purgatory/v2-000* --cc peterz@infradead.org --cc clang-built-linux@googlegroups.com ``` Maybe I should just add `--cc linux-kernel@vger.kernel.org` to my shell function?
On Mon, Jul 22, 2019 at 2:33 PM Nick Desaulniers <ndesaulniers@google.com> wrote: > > 1. Reuse the implementation of memcpy and memset instead of relying on > __builtin_memcpy and __builtin_memset as it causes infinite recursion > in Clang (at any opt level) or GCC at -O2. > 2. Don't reset KBUILD_CFLAGS, rather filter CONFIG_FUNCTION_TRACER flags > via `CFLAGS_REMOVE_<file>.o = -pg`. > > The order of the patches are reversed; in case we ever need to bisect, > the memcpy/memset infinite recursion would occur with just patch 2/2 > applied. > > V2 of: https://lkml.org/lkml/2019/7/17/755 > > Nick Desaulniers (2): > x86/purgatory: do not use __builtin_memcpy and __builtin_memset > x86/purgatory: use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS > > arch/x86/purgatory/Makefile | 15 ++++++++++----- > arch/x86/purgatory/purgatory.c | 6 ++++++ > arch/x86/purgatory/string.c | 23 ----------------------- > 3 files changed, 16 insertions(+), 28 deletions(-) > delete mode 100644 arch/x86/purgatory/string.c > > -- > 2.22.0.657.g960e92d24f-goog >
-- Thanks, ~Nick Desaulniers
| |