From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: mika.penttila@nextfour.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/2 v2] set_memory_xx fixes
Date: Tue, 26 Jan 2016 14:31:02 +0000 [thread overview]
Message-ID: <20160126143102.GP10826@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1453789989-13260-1-git-send-email-mika.penttila@nextfour.com>
On Tue, Jan 26, 2016 at 08:33:07AM +0200, mika.penttila@nextfour.com wrote:
> Recent changes (4.4.0+) in module loader triggered oops on ARM.
>
> The module in question is in-tree module :
> drivers/misc/ti-st/st_drv.ko
I don't see a reason for these to be applied together, they each look
like stand-alone changes.
I'd like to apply the ARM (32-bit) change, but as it incorporates ARM64
changes, I either need an ack from ARM64 people, or I need the ARM64
code split out. Please re-send, copying the ARM64 maintainers too,
optionally splitting the first patch up.
Thanks.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-01-26 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 6:33 [PATCH 0/2 v2] set_memory_xx fixes mika.penttila
2016-01-26 6:33 ` [PATCH 1/2 v2] arm, arm64: change_memory_common with numpages == 0 should be no-op mika.penttila
2016-01-26 6:33 ` [PATCH 2/2 v2] make apply_to_page_range() more robust mika.penttila
2016-01-26 14:31 ` Russell King - ARM Linux [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=20160126143102.GP10826@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mika.penttila@nextfour.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).