public inbox for linux-metag@vger.kernel.org
 help / color / mirror / Atom feed
From: James Hogan <james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
To: Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: linux-metag <linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [GIT PULL] Metag architecture changes for v4.7
Date: Mon, 16 May 2016 11:52:24 +0100	[thread overview]
Message-ID: <5739A668.9040103@imgtec.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

Hi Linus,

Please pull these metag architecture changes for v4.7.

Thanks
James


The following changes since commit b562e44f507e863c6792946e4e1b1449fbbac85d:

  Linux 4.5 (2016-03-13 21:28:54 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jhogan/metag.git tags/metag-for-v4.7

for you to fetch changes up to 096a8b6d5e7ab9f8ca3d2474b3ca6a1fe79e0371:

  metag: Fix atomic_*_return inline asm constraints (2016-05-03 09:25:46 +0100)

----------------------------------------------------------------
Metag architecture changes for v4.7

3 minor fixes:
- removal of stale comment
- fix build for Meta1 when perf events are enabled
- fix inline asm constraint in atomics

----------------------------------------------------------------
James Hogan (2):
      metag: perf: fix build on Meta1
      metag: Fix atomic_*_return inline asm constraints

Li Bin (1):
      metag: ftrace: remove the misleading comment for ftrace_dyn_arch_init

 arch/metag/include/asm/atomic_lnkget.h | 2 +-
 arch/metag/kernel/ftrace.c             | 1 -
 arch/metag/kernel/perf/perf_event.c    | 3 +++
 3 files changed, 4 insertions(+), 2 deletions(-)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2016-05-16 10:52 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=5739A668.9040103@imgtec.com \
    --to=james.hogan-1axoqhu6uovqt0dzr+alfa@public.gmane.org \
    --cc=linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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