From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: Kconfig: remove dependence of CONFIG_DEBUG_RODATA on !kexec
Date: Tue, 20 May 2014 09:35:57 +0100 [thread overview]
Message-ID: <20140520083557.GA21866@arm.com> (raw)
In-Reply-To: <CAGXu5jK_RwA+3H9fSz4u9+hnFVuP5ST9x_sn1hSeNp98SK4TNg@mail.gmail.com>
On Mon, May 19, 2014 at 08:33:51PM +0100, Kees Cook wrote:
> On Fri, May 16, 2014 at 9:49 AM, Will Deacon <will.deacon@arm.com> wrote:
> > On Mon, May 12, 2014 at 10:31:57AM +0100, Nikolay Borisov wrote:
> >> Remove DEBUG_RODATA dependence on !kexec since "ARM: kexec: Make .text R/W in
> >> machine_kexec" fixes the incompatibility between those 2
> >> options.
> >>
> >> Signed-off-by: Nikolay Borisov <Nikolay.Borisov@arm.com>
> >
> > Acked-by: Will Deacon <will.deacon@arm.com>
>
> We've got, from what I can see, about 4 sets of patches that are or
> revolve around DEBUG_RODATA. What do you think is the best way to
> gather everything together? Do you want me to build 1 giant set of
> patches that includes kexec, DEBUG_RODATA, FIXMAP, and kgdb all
> together, or should we just start flushing each one separately into
> the patch tracker?
It's probably worth you collating the patches together into a single series,
giving it some testing, then reposting that to the list. Then, assuming
nothing explodes, sending a pull request to rmk (although it's getting quite
late in the day for 3.16).
Sound like a plan?
Will
next prev parent reply other threads:[~2014-05-20 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 9:31 [PATCH 1/2] ARM: kexec: Make .text R/W in machine_kexec Nikolay Borisov
2014-05-12 9:31 ` [PATCH 2/2] ARM: Kconfig: remove dependence of CONFIG_DEBUG_RODATA on !kexec Nikolay Borisov
2014-05-16 16:49 ` Will Deacon
2014-05-19 19:33 ` Kees Cook
2014-05-20 8:35 ` Will Deacon [this message]
2014-05-21 4:11 ` Kees Cook
2014-05-16 16:48 ` [PATCH 1/2] ARM: kexec: Make .text R/W in machine_kexec Will Deacon
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=20140520083557.GA21866@arm.com \
--to=will.deacon@arm.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).