From: Greg Ungerer <gerg@linux-m68k.org>
To: torvalds@linux-foundation.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [git pull] m68knommu changes for v5.6
Date: Thu, 6 Feb 2020 14:13:50 +1000 [thread overview]
Message-ID: <70537bf1-51e2-e668-4d82-7e4ab73abbca@linux-m68k.org> (raw)
Hi Linus,
Can you please pull the m68knommu git tree, for-next branch.
A couple of changes. One to remove old CONFIG options from the
m68knommu defconfig files. Another to fix a warning in the m68k
non-MMU get_user() macro.
Regards
Greg
The following changes since commit def9d2780727cec3313ed3522d0123158d87224d:
Linux 5.5-rc7 (2020-01-19 16:02:49 -0800)
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 8044aad70a1fbd66376cdb2a13e536db9dd6c132:
m68knommu: fix memcpy() out of bounds warning in get_user() (2020-02-03 14:43:35 +1000)
----------------------------------------------------------------
Greg Ungerer (1):
m68knommu: fix memcpy() out of bounds warning in get_user()
Krzysztof Kozlowski (1):
m68k: configs: Cleanup old Kconfig IO scheduler options
arch/m68k/configs/amcore_defconfig | 1 -
arch/m68k/configs/m5208evb_defconfig | 2 --
arch/m68k/configs/m5249evb_defconfig | 2 --
arch/m68k/configs/m5272c3_defconfig | 2 --
arch/m68k/configs/m5275evb_defconfig | 2 --
arch/m68k/configs/m5307c3_defconfig | 2 --
arch/m68k/configs/m5407c3_defconfig | 2 --
arch/m68k/configs/m5475evb_defconfig | 2 --
arch/m68k/include/asm/uaccess_no.h | 19 +++++++++++--------
9 files changed, 11 insertions(+), 23 deletions(-)
next reply other threads:[~2020-02-06 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 4:13 Greg Ungerer [this message]
2020-02-06 8:20 ` [git pull] m68knommu changes for v5.6 pr-tracker-bot
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=70537bf1-51e2-e668-4d82-7e4ab73abbca@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@linux-foundation.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).