linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Klaus Kusche <klaus.kusche@computerix.info>
To: keescook@chromium.org, johannes.hirte@datenkhaos.de
Cc: bp@suse.de, samitolvanen@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/build: Move _etext to actual end of .text
Date: Sun, 9 Jun 2019 11:35:03 +0200	[thread overview]
Message-ID: <502d5b36-e0d0-ffcc-5dd4-35db9d033561@computerix.info> (raw)


Hello,

Same problem for linux 5.1.7: 
Kernel building fails with the same relocation error.

5.1.5 does not have the problem, builds fine for me.

Is there anything I can do to investigate the problem?


-- 
Prof. Dr. Klaus Kusche
Private address: Rosenberg 41, 07546 Gera, Germany
+49 365 20413058 klaus.kusche@computerix.info https://www.computerix.info
Office address: DHGE Gera, Weg der Freundschaft 4, 07546 Gera, Germany
+49 365 4341 306 klaus.kusche@dhge.de https://www.dhge.de

             reply	other threads:[~2019-06-09  9:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09  9:35 Klaus Kusche [this message]
2019-06-09 18:40 ` [PATCH] x86/build: Move _etext to actual end of .text Johannes Hirte
2019-06-19 18:37   ` Ross Zwisler
2019-06-20 17:58     ` Kees Cook
  -- strict thread matches above, loose matches on Subject: below --
2019-06-05 16:08 Alec Ari
2019-06-05 18:16 ` Kees Cook
2019-06-05 18:43   ` Greg KH
2019-06-01  8:51 Klaus Kusche
2019-04-23 18:38 Kees Cook
2019-05-14 12:04 ` Johannes Hirte
2019-05-14 15:43   ` Kees Cook
2019-05-14 16:10     ` Johannes Hirte
2019-05-15 18:54       ` Kees Cook
2019-05-16 13:56         ` Johannes Hirte
2019-05-16 17:51           ` Kees Cook

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=502d5b36-e0d0-ffcc-5dd4-35db9d033561@computerix.info \
    --to=klaus.kusche@computerix.info \
    --cc=bp@suse.de \
    --cc=johannes.hirte@datenkhaos.de \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samitolvanen@google.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;
as well as URLs for NNTP newsgroup(s).