From: 陈华才 <chenhc@lemote.com>
To: "Tony Lindgren" <tony@atomide.com>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Rich Felker" <dalias@libc.org>,
"Russell King" <linux@arm.linux.org.uk>,
"Yoshinori Sato" <ysato@users.sourceforge.jp>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Ralf Baechle" <ralf@linux-mips.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-omap <linux-omap@vger.kernel.org>,
"Fabio Estevam" <festevam@gmail.com>,
"James Hogan" <james.hogan@mips.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Regression with arm in next with stack protector
Date: Tue, 27 Mar 2018 16:29:12 +0800 [thread overview]
Message-ID: <tencent_1DDCF65B56759D1B570EF7DD@qq.com> (raw)
In-Reply-To: <20180326153714.GG5700@atomide.com>
Allwinner devices are OK, Exynos devices (except 4210) are OK.
------------------ Original ------------------
From: "Tony Lindgren"<tony@atomide.com>;
Date: Mon, Mar 26, 2018 11:37 PM
To: "陈华才"<chenhc@lemote.com>;
Cc: "Andrew Morton"<akpm@linux-foundation.org>; "Fabio Estevam"<festevam@gmail.com>; "Stephen Rothwell"<sfr@canb.auug.org.au>; "Rich Felker"<dalias@libc.org>; "Russell King"<linux@arm.linux.org.uk>; "Yoshinori Sato"<ysato@users.sourceforge.jp>; "linux-kernel"<linux-kernel@vger.kernel.org>; "Ralf Baechle"<ralf@linux-mips.org>; "linux-omap"<linux-omap@vger.kernel.org>; "James Hogan"<james.hogan@mips.com>; "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"<linux-arm-kernel@lists.infradead.org>;
Subject: Re: Regression with arm in next with stack protector
* 陈华才 <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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-03-27 8:29 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
2018-03-27 8:29 ` 陈华才 [this message]
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=tencent_1DDCF65B56759D1B570EF7DD@qq.com \
--to=chenhc@lemote.com \
--cc=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=festevam@gmail.com \
--cc=james.hogan@mips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.com \
--cc=ysato@users.sourceforge.jp \
/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