linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Kees Cook <keescook@chromium.org>,
	Anton Vorontsov <cbouatmailru@gmail.com>,
	Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] pstore/ram for 3.11
Date: Wed, 12 Jun 2013 22:44:44 -0500	[thread overview]
Message-ID: <51B9402C.5070300@gmail.com> (raw)

Not sure who takes this, but please pull these 2 changes for pstore for
3.11. These are necessary to get pstore to work with on-chip RAM on
Calxeda highbank platform.

I dropped the write-combine change from this series. While write-combine
is technically the correct mapping needed for ARM, it doesn't solve any
problem for me.

Rob

The following changes since commit c7788792a5e7b0d5d7f96d0766b4cb6112d47d75:

  Linux 3.10-rc2 (2013-05-20 14:37:38 -0700)

are available in the git repository at:

  git://sources.calxeda.com/kernel/linux.git tags/pstore-for-3.11

for you to fetch changes up to da98a8882b3b388e9580821c8ad281c85f94d025:

  pstore/ram: avoid atomic accesses for ioremapped regions (2013-05-21
15:32:44 -0500)

----------------------------------------------------------------
2 changes for pstore ram:

- Don't use atomic ops on ioremapped RAM which is not supported on ARM
- Allow non-power of 2 sized RAM buffers

----------------------------------------------------------------
Rob Herring (2):
      pstore/ram: remove the power of buffer size limitation
      pstore/ram: avoid atomic accesses for ioremapped regions

 fs/pstore/ram.c      |  2 --
 fs/pstore/ram_core.c | 54
++++++++++++++++++++++++++++++++++++++++++++++++++--
 2 files changed, 52 insertions(+), 4 deletions(-)

             reply	other threads:[~2013-06-13  3:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  3:44 Rob Herring [this message]
2013-06-14 22:18 ` [GIT PULL] pstore/ram for 3.11 Tony Luck
2013-06-14 22:32   ` Rob Herring
2013-06-14 22:47     ` Anton Vorontsov
2013-06-14 22:57       ` Tony Luck

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=51B9402C.5070300@gmail.com \
    --to=robherring2@gmail.com \
    --cc=cbouatmailru@gmail.com \
    --cc=ccross@android.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    /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).