From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Renaud Barbier <Renaud.Barbier@ametek.com>,
Barebox List <barebox@lists.infradead.org>
Subject: Re: Subject: [PATCH 0/1] Initial NVME storage erase operation
Date: Thu, 16 Jan 2025 12:15:36 +0100 [thread overview]
Message-ID: <367c134c-8614-47a0-8e84-0ccda8d01b62@pengutronix.de> (raw)
In-Reply-To: <DM5PR07MB3532F89A244DCCEEB887707DEC1A2@DM5PR07MB3532.namprd07.prod.outlook.com>
Hello Renaud,
On 16.01.25 11:52, Renaud Barbier wrote:
> This patch introduces the erase entry point for the NVME storage.
> It uses the nvme sanitize command 2 for a low level block erase
> of the entire device as start and end blocks cannot be specified.
>
> Note that in the current state, the user should first remove existing
> partitions with the command 'parted rmpart' as they will stay dangling
> in barebox device nodes and mount points.
Thanks for your patch. Your mailer seems to have mangled the series
a bit:
- The patch is not a reply to the cover letter
- "Subject: [PATCH 0/1]" ends up in the commit message title
I think Sascha can fix it up on apply, but jfyi, you can use b4 with barebox
now, including the kernel.org web relay:
https://b4.docs.kernel.org/en/latest/contributor/send.html#authenticating-with-the-web-submission-endpoint
This takes care to send patches unmangled by corporate IT.
Cheers,
Ahmad
>
> Renaud Barbier (1):
> nvme: add erase operation through sanitize command
>
> drivers/nvme/host/core.c | 82 ++++++++++++++++++++++++++++++++++++++++
> drivers/nvme/host/pci.c | 2 +
> include/nvme/types.h | 38 +++++++++++++++++++
> 3 files changed, 122 insertions(+)
> create mode 100644 include/nvme/types.h
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-01-16 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 10:52 Renaud Barbier
2025-01-16 11:15 ` Ahmad Fatoum [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=367c134c-8614-47a0-8e84-0ccda8d01b62@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=Renaud.Barbier@ametek.com \
--cc=barebox@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox