NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Dan Williams <dan.j.williams@intel.com>,
	 Vishal Verma <vishal.l.verma@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	 Ira Weiny <ira.weiny@intel.com>,
	Oliver O'Halloran <oohall@gmail.com>
Cc: nvdimm@lists.linux.dev, kernel@pengutronix.de
Subject: Re: [PATCH 0/2] nvdimm: Convert to platform remove callback returning void
Date: Mon, 29 Apr 2024 09:33:16 +0200	[thread overview]
Message-ID: <dgye5olc5ofqlxvtouiw4pl4b3sf7gnego7bhf2fa57knjkv6y@xom44xpshmcs> (raw)
In-Reply-To: <cover.1712756722.git.u.kleine-koenig@pengutronix.de>

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

Hello,

On Wed, Apr 10, 2024 at 03:47:32PM +0200, Uwe Kleine-König wrote:
> this series converts all platform drivers below drivers/nvdimm/ to not
> use struct platform_device::remove() any more. See commit 5c5a7680e67b
> ("platform: Provide a remove callback that returns no value") for an
> extended explanation and the eventual goal.
> 
> All conversations are trivial, because the driver's .remove() callbacks
> returned zero unconditionally.
> 
> There are no interdependencies between these patches, so they can be
> applied independently if needed. This is merge window material.

I intend to send the change adapting the prototype of struct
platform_device::remove() soon after the upcoming merge window closed.
So it would be great if these two patches made it in before. If not,
I'll ask Greg to take these patches together with the change to struct
platform_device.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2024-04-29  7:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 13:47 [PATCH 0/2] nvdimm: Convert to platform remove callback returning void Uwe Kleine-König
2024-04-10 13:47 ` [PATCH 1/2] nvdimm/e820: " Uwe Kleine-König
2024-04-10 13:47 ` [PATCH 2/2] nvdimm/of_pmem: " Uwe Kleine-König
2024-04-10 15:33 ` [PATCH 0/2] nvdimm: " Dave Jiang
2024-04-29  7:33 ` Uwe Kleine-König [this message]

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=dgye5olc5ofqlxvtouiw4pl4b3sf7gnego7bhf2fa57knjkv6y@xom44xpshmcs \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=kernel@pengutronix.de \
    --cc=nvdimm@lists.linux.dev \
    --cc=oohall@gmail.com \
    --cc=vishal.l.verma@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 read-only IMAP folder(s) and NNTP newsgroup(s).