From: Guenter Roeck <linux@roeck-us.net>
To: torvalds@linuxfoundation.org
Cc: Guan Xuetao <gxt@mprc.pku.edu.cn>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-kernel@vger.kernel.org,
uclinux-h8-devel@lists.sourceforge.jp
Subject: [GIT PULL] Architecture fixes for v4.8
Date: Sat, 13 Aug 2016 16:51:54 -0700 [thread overview]
Message-ID: <1471132314-14742-1-git-send-email-linux@roeck-us.net> (raw)
Hi Linus,
Please consider pulling generic architecture fixes for Linux v4.8 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git fixes-for-linus-4.8
There are two patches in this series. Both have been in -next through maintainer
branches for a while, and I picked them up as-is from there.
unicore32 builds have been broken since v4.6. The fix has been available
in -next since March of this year.
h8300 builds have been broken since the last commit window. The fix has been
available in -next since June of this year.
Thanks,
Guenter
------
The following changes since commit f31494bd05b06b0cdb4da6aebe92eaafab970df6:
Merge tag 'vfio-v4.8-rc2' of git://github.com/awilliam/linux-vfio (2016-08-12 16:34:58 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git tags/fixes-for-linus-4.8
for you to fetch changes up to 2b05980d895e51fc46d3d27c8d1bcc696dddca99:
h8300: Add missing include file to asm/io.h (2016-08-13 08:53:56 -0700)
----------------------------------------------------------------
h8300 and unicore32 architecture fixes
Two patches to fix h8300 and unicore32 builds.
----------------------------------------------------------------
Guenter Roeck (2):
unicore32: mm: Add missing parameter to arch_vma_access_permitted
h8300: Add missing include file to asm/io.h
arch/h8300/include/asm/io.h | 2 ++
arch/unicore32/include/asm/mmu_context.h | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
reply other threads:[~2016-08-14 10:08 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=1471132314-14742-1-git-send-email-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gxt@mprc.pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linuxfoundation.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®