From: Borislav Petkov <bp@alien8.de>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Petr Pavlu <petr.pavlu@suse.com>,
tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
nicolas@fjasle.eu, masahiroy@kernel.org,
kirill.shutemov@linux.intel.com, tony.luck@intel.com,
michael.roth@amd.com, nathan@kernel.org, ndesaulniers@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86: Avoid relocation information in final vmlinux
Date: Wed, 23 Nov 2022 15:38:28 +0100 [thread overview]
Message-ID: <Y34wZF2tute+pyKk@zn.tnic> (raw)
In-Reply-To: <Y34gw8tCCZgjBwUM@debian.me>
On Wed, Nov 23, 2022 at 08:31:47PM +0700, Bagas Sanjaya wrote:
> Why do you say "tautologically useless"?
Do you want a hint and think about it a bit or should I tell you
directly what this means?
> I think even Documentation/process/submitting-patches.rst doesn't
> describe why.
Execute the grep command above and read the text around the results.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-11-23 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 8:46 [PATCH v2] x86: Avoid relocation information in final vmlinux Petr Pavlu
2022-11-23 12:30 ` Borislav Petkov
2022-11-23 13:31 ` Bagas Sanjaya
2022-11-23 14:38 ` Borislav Petkov [this message]
2022-11-23 15:43 ` Petr Pavlu
2022-11-23 15:54 ` Borislav Petkov
2022-11-23 17:45 ` H. Peter Anvin
2022-11-24 10:03 ` Petr Pavlu
2022-11-24 9:21 ` Petr Pavlu
2022-11-24 12:38 ` Borislav Petkov
2022-11-24 13:33 ` Petr Pavlu
2022-11-24 15:41 ` Borislav Petkov
2022-11-25 16:41 ` Borislav Petkov
2022-11-25 19:25 ` Borislav Petkov
2022-11-28 14:38 ` Petr Pavlu
2023-06-14 18:42 ` [tip: x86/build] x86/build: " tip-bot2 for Petr Pavlu
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=Y34wZF2tute+pyKk@zn.tnic \
--to=bp@alien8.de \
--cc=bagasdotme@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=petr.pavlu@suse.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.