From: Kanchan Joshi <joshi.k@samsung.com>
To: kbusch@kernel.org, hch@lst.de, sagi@grimberg.me
Cc: linux-nvme@lists.infradead.org, Kanchan Joshi <joshi.k@samsung.com>
Subject: [PATCH 1/2] nvme: remove sgs and sws
Date: Thu, 2 May 2024 12:04:37 +0530 [thread overview]
Message-ID: <20240502063438.422046-2-joshi.k@samsung.com> (raw)
In-Reply-To: <20240502063438.422046-1-joshi.k@samsung.com>
sgs/sws are unused, so remove these from nvme_ns_head structure.
Signed-off-by: Kanchan Joshi <joshi.k@samsung.com>
---
drivers/nvme/host/nvme.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/nvme/host/nvme.h b/drivers/nvme/host/nvme.h
index d0ed64dc7380..22a9992a4525 100644
--- a/drivers/nvme/host/nvme.h
+++ b/drivers/nvme/host/nvme.h
@@ -466,8 +466,6 @@ struct nvme_ns_head {
u8 pi_type;
u8 pi_offset;
u8 guard_type;
- u16 sgs;
- u32 sws;
#ifdef CONFIG_BLK_DEV_ZONED
u64 zsze;
#endif
--
2.25.1
next prev parent reply other threads:[~2024-05-02 6:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240502064149epcas5p4be127b8e22874b76bb41ce25c29263f9@epcas5p4.samsung.com>
2024-05-02 6:34 ` [PATCH 0/2] cleanup Kanchan Joshi
[not found] ` <CGME20240502064150epcas5p3b6461ca0466650cd0296089d257ff861@epcas5p3.samsung.com>
2024-05-02 6:34 ` Kanchan Joshi [this message]
2024-05-02 7:12 ` [PATCH 1/2] nvme: remove sgs and sws Christoph Hellwig
2024-05-03 7:36 ` Sagi Grimberg
[not found] ` <CGME20240502064151epcas5p3834c50bcaea2c8db2d24fc30b0957ff0@epcas5p3.samsung.com>
2024-05-02 6:34 ` [PATCH 2/2] nvme: reduce a repeated ZNS check Kanchan Joshi
2024-05-02 7:13 ` Christoph Hellwig
2024-05-02 8:44 ` Kanchan Joshi
2024-05-03 7:38 ` Sagi Grimberg
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=20240502063438.422046-2-joshi.k@samsung.com \
--to=joshi.k@samsung.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).