linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression with arm in next with stack protector
Date: Mon, 26 Mar 2018 08:37:14 -0700	[thread overview]
Message-ID: <20180326153714.GG5700@atomide.com> (raw)
In-Reply-To: <tencent_79FD53B203715FD7439C6EAB@qq.com>

* ??? <chenhc@lemote.com> [180326 06:59]:
> Hi, Tony and Fabio,
> 
> Could you please upload your kernel binary to somewhere for me? I don't understand why some ARM boards is OK while others are broken.

Well the kernel I'm testing is just current Linux next cross
compiled omap2plus_defconfig kernel. I do have few more config
options enabled like LOCKDEP and DEBUG_ATOMIC_SLEEP, but I
doubt they matter here :)

Then I'm using gcc-7.3.0 and binutils-2.30 built with the
buildall.git scripts:

git://git.infradead.org/users/segher/buildall.git

If you still need binaries, let me know.

Do you know which arm devices are working with your patch?

Regards,

Tony

  reply	other threads:[~2018-03-26 15:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 18:14 Regression with arm in next with stack protector Tony Lindgren
2018-03-23 18:45 ` Fabio Estevam
2018-03-23 19:15   ` Andrew Morton
2018-03-23 22:31     ` Stephen Rothwell
2018-03-26  6:57     ` 陈华才
2018-03-26 15:37       ` Tony Lindgren [this message]
2018-03-27  8:29         ` 陈华才
2018-03-27  9:04 ` Russell King - ARM Linux
2018-03-27  9:11   ` Russell King - ARM Linux
2018-03-27 11:34   ` Russell King - ARM Linux
2018-03-27 15:36     ` Rich Felker
2018-03-27 15:35   ` Rich Felker
2018-03-27 17:20     ` Russell King - ARM Linux
2018-03-27 17:27       ` Rich Felker

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=20180326153714.GG5700@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).