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.8
Date: Thu, 11 Jun 2020 15:21:29 +1000 [thread overview]
Message-ID: <3dc0ca7e-9c44-adac-a3c4-53ab6e0288e5@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu changes for v5.8.
Regards
Greg
The following changes since commit 9cb1fd0efd195590b828b9b865421ad345a4a145:
Linux 5.7-rc7 (2020-05-24 15:32:54 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-for-v5.8
for you to fetch changes up to 9e2b6ed41f8f99c97b13c9d15cbef235dbd97fb6:
m68k,nommu: fix implicit cast from __user in __{get,put}_user_asm() (2020-05-30 10:55:54 +1000)
----------------------------------------------------------------
m68knommu: collection of fixes for v5.8
Fixes include:
. casting clean up in the user access macros
. memory leak on error case fix for PCI probing
. update of a defconfig.
----------------------------------------------------------------
Bin Meng (1):
m68k: Drop CONFIG_MTD_M25P80 in stmark2_defconfig
Christophe JAILLET (1):
m68k/PCI: Fix a memory leak in an error handling path
Luc Van Oostenryck (2):
m68k,nommu: add missing __user in uaccess' __ptr() macro
m68k,nommu: fix implicit cast from __user in __{get,put}_user_asm()
arch/m68k/coldfire/pci.c | 4 +++-
arch/m68k/configs/stmark2_defconfig | 1 -
arch/m68k/include/asm/uaccess_no.h | 6 +++---
3 files changed, 6 insertions(+), 5 deletions(-)
next reply other threads:[~2020-06-11 5:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 5:21 Greg Ungerer [this message]
2020-06-11 22:00 ` [git pull] m68knommu changes for v5.8 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=3dc0ca7e-9c44-adac-a3c4-53ab6e0288e5@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).