Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: [GIT PULL] libnvdimm fixes for 4.6-rc3
Date: Sat, 9 Apr 2016 17:48:25 +0000	[thread overview]
Message-ID: <1460224104.6400.12.camel@intel.com> (raw)

Hi Linus, please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes

...to receive 3 fixes, the first 2 are tagged for -stable.

1/ The ndctl utility/library gained expanded unit tests illuminating a
long standing bug in the libnvdimm SMART data retrieval implementation.
 It has been broken since its initial implementation, now fixed.

2/ Another one line fix for the detection of stale info blocks.
 Without this change userspace can get into a situation where it is
unable to reconfigure a namespace.

3/ Fix the badblock initialization path in the presence of the new (in
4,6-rc1) section alignment workarounds.  Without this change badblocks
will be reported at the wrong offset.

These have received a build success report from the kbuild robot and
have appeared in -next with no reported issues.

The following changes since commit 9735a22799b9214d17d3c231fe377fc852f042e9:

  Linux 4.6-rc2 (2016-04-03 09:09:40 -0500)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes

for you to fetch changes up to a390180291dd9a2392bbab4242cde712c326efc6:

  libnvdimm, pfn: fix nvdimm_namespace_add_poison() vs section alignment (2016-04-07 20:02:06 -0700)

----------------------------------------------------------------
Dan Williams (3):
      libnvdimm: fix smart data retrieval
      libnvdimm, pfn: fix uuid validation
      libnvdimm, pfn: fix nvdimm_namespace_add_poison() vs section alignment

 drivers/nvdimm/bus.c      |  2 +-
 drivers/nvdimm/core.c     | 41 ++++++++++++++++++++---------------------
 drivers/nvdimm/nd.h       |  4 ++--
 drivers/nvdimm/pfn_devs.c |  2 +-
 drivers/nvdimm/pmem.c     | 36 +++++++++++++++++++++++++++++-------
 5 files changed, 53 insertions(+), 32 deletions(-)
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

                 reply	other threads:[~2016-04-09 17:48 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=1460224104.6400.12.camel@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.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