From: Greg Ungerer <gerg@uclinux.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
uClinux development list <uclinux-dev@uclinux.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [git pull] m68knommu/coldfire fixes for 4.4
Date: Mon, 9 Nov 2015 13:06:01 +1000 [thread overview]
Message-ID: <56400D99.4020309@uclinux.org> (raw)
Hi Linus,
Can you please pull the m68knommu git tree, for-next branch.
Only a single patch, fixes brk area setup problem in nommu environments.
Regards
Greg
The following changes since commit 32b88194f71d6ae7768a29f87fbba454728273ee:
Linux 4.3-rc7 (2015-10-25 10:39:47 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git for-next
for you to fetch changes up to 4ac313111018cb44ecc250445de5ccb93026a980:
fs/binfmt_elf_fdpic.c: fix brk area overlap with stack on NOMMU (2015-10-26 09:02:32 +1000)
----------------------------------------------------------------
Rich Felker (1):
fs/binfmt_elf_fdpic.c: fix brk area overlap with stack on NOMMU
fs/binfmt_elf_fdpic.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
reply other threads:[~2015-11-09 3:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56400D99.4020309@uclinux.org \
--to=gerg@uclinux.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-dev@uclinux.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