From: Thomas Gleixner <tglx@linutronix.de>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [PATCH v4 0/2] Support kexec/kdump for clang built kernel
Date: Fri, 26 Jul 2019 01:09:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1907260105280.1791@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAKwvOdnBKcEFkv2qEWPaFEjPSmR_SXBo2ZGz7ho9pBc88dZJBA@mail.gmail.com>
On Thu, 25 Jul 2019, Nick Desaulniers wrote:
> On Thu, Jul 25, 2019 at 3:51 PM Thomas Gleixner <tglx@linutronix.de> wrote:
> > On Thu, 25 Jul 2019, Nick Desaulniers wrote:
> >
> > I'm really impressed how you manage to make the cover letter (0/N) a reply
> > to 1/N instead of 1..N/N being a reply to 0/N.
> >
> > In-Reply-To: <20190725200625.174838-1-ndesaulniers@google.com>
> > Message-Id: <20190725200625.174838-3-ndesaulniers@google.com>
> >
> > Is that a new git feature to be $corp top-posting compliant?
>
> It appears to be a hidden bonus feature of:
> $ git-send-email purgatory/v4-000*
Care to poke the git folks?
> > > V4 of: https://lkml.org/lkml/2019/7/23/864
> >
> > Please don't use lkml.org references. I know it's popular but equally
> > unreliable at times.
>
> Oh?
404 or silent fail are happening on a regular base and of course always
when you really need that information. Murphy's law ...
Thanks,
tglx
prev parent reply other threads:[~2019-07-25 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 20:06 [PATCH v4 1/2] x86/purgatory: do not use __builtin_memcpy and __builtin_memset Nick Desaulniers
2019-07-25 20:06 ` [PATCH v4 2/2] x86/purgatory: use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS Nick Desaulniers
2019-07-26 8:54 ` Thomas Gleixner
2019-08-07 13:17 ` Thomas Gleixner
2019-07-25 20:06 ` [PATCH v4 0/2] Support kexec/kdump for clang built kernel Nick Desaulniers
2019-07-25 22:51 ` Thomas Gleixner
2019-07-25 22:57 ` Nick Desaulniers
2019-07-25 23:09 ` Thomas Gleixner [this message]
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=alpine.DEB.2.21.1907260105280.1791@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=yamada.masahiro@socionext.com \
/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
all inboxes | Powered by JetHome®