linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	anton@samba.org, imunsie@au1.ibm.com
Subject: [git pull] Please pull mpe/linux.git powerpc-3.19-4 tag
Date: Thu, 15 Jan 2015 17:28:34 +1100	[thread overview]
Message-ID: <1421303314.11409.8.camel@ellerman.id.au> (raw)

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

Hi Linus,

Please pull some more powerpc fixes for 3.19:

The following changes since commit eaa27f34e91a14cdceed26ed6c6793ec1d186115:

  linux 3.19-rc4 (2015-01-11 12:44:53 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux.git tags/powerpc-3.19-4

for you to fetch changes up to a87e810f61b49f19bd29ea564b7cd1e92e43d989:

  powerpc: Work around gcc bug in current_thread_info() (2015-01-12 16:40:02 +1100)

----------------------------------------------------------------
Anton Blanchard (1):
      powernv: Fix OPAL tracepoint code

Ian Munsie (1):
      cxl: Fix issues when unmapping contexts

Michael Ellerman (1):
      powerpc: Work around gcc bug in current_thread_info()

 arch/powerpc/include/asm/thread_info.h         | 13 ++--
 arch/powerpc/platforms/powernv/opal-wrappers.S |  1 -
 drivers/misc/cxl/context.c                     | 82 ++++++++++++++++++++------
 drivers/misc/cxl/file.c                        | 14 +++--
 4 files changed, 78 insertions(+), 32 deletions(-)



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2015-01-15  6:28 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=1421303314.11409.8.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=anton@samba.org \
    --cc=imunsie@au1.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).