From: Michal Simek <michal.simek@xilinx.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] arch/microblaze changes for 4.3-rc1
Date: Thu, 10 Sep 2015 07:01:28 +0200 [thread overview]
Message-ID: <55F10EA8.3040602@xilinx.com> (raw)
Hi Linus,
please pull this one patch to your tree. I have rebased the branch
because there was a conflict with
"tile: enable full SECCOMP support"
(sha1: a0ddef81f4aeeeec3326f6b6a255d8ea13b41908).
Thanks,
Michal
The following changes since commit b8889c4fc6ba03e289cec6a4d692f6f080a55e53:
Merge tag 'tty-4.3-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty (2015-09-09
11:27:01 -0700)
are available in the git repository at:
git://git.monstr.eu/linux-2.6-microblaze.git next
for you to fetch changes up to b14132797d8041a42e03f4ffa1e722da1425adfb:
elf-em.h: move EM_MICROBLAZE to the common header (2015-09-10 06:54:15
+0200)
----------------------------------------------------------------
Mike Frysinger (1):
elf-em.h: move EM_MICROBLAZE to the common header
arch/microblaze/include/uapi/asm/elf.h | 3 ++-
include/uapi/linux/elf-em.h | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
reply other threads:[~2015-09-10 5:02 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=55F10EA8.3040602@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.