From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: shmobile: Move written variables from .text to .data
Date: Thu, 28 Jan 2016 11:07:48 -0800 [thread overview]
Message-ID: <20160128190748.GJ19432@atomide.com> (raw)
In-Reply-To: <20160128174848.GO10826@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [160128 09:50]:
> On Thu, Jan 28, 2016 at 07:19:34AM -0800, Kees Cook wrote:
> >
> > And FWIW, I've now got the RODATA patch back in the patch queue, since
> > we're at -rc1:
> > http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8501/1
>
> And I'll be dropping it into linux-next for next week (iow, I'll commit
> it tomorrow.)
>
> Unfortunately, -rc1 broke some platforms, so Olof's builder isn't going
> to get full coverage of it while building only my tree.
FYI I sent a pull request for the omap related fixes earlier today. So
we should be good to go from that point of view for enabling rodata by
default for v4.6.
Regards,
Tony
prev parent reply other threads:[~2016-01-28 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 15:04 [PATCH 0/2] ARM: shmobile: Move written variables from .text to .data Geert Uytterhoeven
2016-01-28 15:04 ` [PATCH 1/2] ARM: shmobile: Move shmobile_scu_base " Geert Uytterhoeven
2016-01-28 15:37 ` Sergei Shtylyov
2016-01-28 17:00 ` Geert Uytterhoeven
2016-01-28 15:04 ` [PATCH 2/2] ARM: shmobile: Move shmobile_smp_{mpidr, fn, arg}[] " Geert Uytterhoeven
2016-01-28 16:30 ` [PATCH 2/2] ARM: shmobile: Move shmobile_smp_{mpidr,fn,arg}[] " Nicolas Pitre
2016-01-28 15:19 ` [PATCH 0/2] ARM: shmobile: Move written variables " Kees Cook
2016-01-28 17:48 ` Russell King - ARM Linux
2016-01-28 19:07 ` Tony Lindgren [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=20160128190748.GJ19432@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 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.