All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NVDIMM <nvdimm@lists.linux.dev>, linux-cxl@vger.kernel.org
Subject: [GIT PULL] NVDIMM + CXL fixes for v5.18-rc2
Date: Sat, 9 Apr 2022 16:46:56 -0700	[thread overview]
Message-ID: <CAPcyv4gLVHZSJNPcxcb6tDD3z8DO_X49OvV-cudeziKfG_08mw@mail.gmail.com> (raw)

Hi Linus, please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/cxl+nvdimm-for-5.18-rc2

...to pick up a couple fixups for code that went in during the merge
window. These did not appear in -next yet, but they have seen kbuild
robot exposure.

---

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/cxl+nvdimm-for-5.18-rc2

for you to fetch changes up to d28820419ca332f856cdf8bef0cafed79c29ed05:

  cxl/pci: Drop shadowed variable (2022-04-08 12:59:43 -0700)

----------------------------------------------------------------
cxl + nvdimm fixes for v5.18-rc2

- Fix a compile error in the nvdimm unit tests

- Fix a shadowed variable warning in the CXL PCI driver

----------------------------------------------------------------
Dan Williams (2):
      tools/testing/nvdimm: Fix security_init() symbol collision
      cxl/pci: Drop shadowed variable

 drivers/cxl/pci.c                | 1 -
 tools/testing/nvdimm/test/nfit.c | 4 ++--
 2 files changed, 2 insertions(+), 3 deletions(-)

             reply	other threads:[~2022-04-09 23:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09 23:46 Dan Williams [this message]
2022-04-10  4:53 ` [GIT PULL] NVDIMM + CXL fixes for v5.18-rc2 pr-tracker-bot

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=CAPcyv4gLVHZSJNPcxcb6tDD3z8DO_X49OvV-cudeziKfG_08mw@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --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 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.