All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: fix for -rc3
Date: Fri, 10 Jun 2016 14:38:50 +0100	[thread overview]
Message-ID: <20160610133850.GA14364@arm.com> (raw)

Hi Linus,

Please pull this arm64 fix for -rc3. It's a fix for an issue that Alex
saw whilst swapping with hardware access/dirty bit support enabled in
the kernel.

Cheers,

Will

--->8

The following changes since commit af8c34ce6ae32addda3788d54a7e340cad22516b:

  Linux 4.7-rc2 (2016-06-05 14:31:26 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to 0106d456c4cb1770253fefc0ab23c9ca760b43f7:

  arm64: mm: always take dirty state from new pte in ptep_set_access_flags (2016-06-08 10:23:44 +0100)

----------------------------------------------------------------
arm64 fix:

- Fix an issue where we fail to fault in old pages on a write when
  CONFIG_ARM64_HW_AFDBM is enabled

----------------------------------------------------------------
Will Deacon (1):
      arm64: mm: always take dirty state from new pte in ptep_set_access_flags

 arch/arm64/mm/fault.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
	agraf@suse.de
Subject: [GIT PULL] arm64: fix for -rc3
Date: Fri, 10 Jun 2016 14:38:50 +0100	[thread overview]
Message-ID: <20160610133850.GA14364@arm.com> (raw)

Hi Linus,

Please pull this arm64 fix for -rc3. It's a fix for an issue that Alex
saw whilst swapping with hardware access/dirty bit support enabled in
the kernel.

Cheers,

Will

--->8

The following changes since commit af8c34ce6ae32addda3788d54a7e340cad22516b:

  Linux 4.7-rc2 (2016-06-05 14:31:26 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to 0106d456c4cb1770253fefc0ab23c9ca760b43f7:

  arm64: mm: always take dirty state from new pte in ptep_set_access_flags (2016-06-08 10:23:44 +0100)

----------------------------------------------------------------
arm64 fix:

- Fix an issue where we fail to fault in old pages on a write when
  CONFIG_ARM64_HW_AFDBM is enabled

----------------------------------------------------------------
Will Deacon (1):
      arm64: mm: always take dirty state from new pte in ptep_set_access_flags

 arch/arm64/mm/fault.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2016-06-10 13:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10 13:38 Will Deacon [this message]
2016-06-10 13:38 ` [GIT PULL] arm64: fix for -rc3 Will Deacon
  -- strict thread matches above, loose matches on Subject: below --
2018-09-07 15:45 Will Deacon
2018-09-07 15:45 ` Will Deacon
2018-09-07 17:51 ` Linus Torvalds
2018-09-07 17:51   ` Linus Torvalds
2018-09-10 17:45   ` Will Deacon
2018-09-10 17:45     ` Will Deacon
2018-09-11 18:45     ` Linus Torvalds
2018-09-11 18:45       ` Linus Torvalds

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=20160610133850.GA14364@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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.