Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 2/3] nvme: change data type of lba_shift
Date: Tue, 30 Jul 2024 16:01:37 +0530	[thread overview]
Message-ID: <20240730103138.66714-3-joshi.k@samsung.com> (raw)
In-Reply-To: <20240730103138.66714-1-joshi.k@samsung.com>

u8 fits the need, so stop using int for it.

Signed-off-by: Kanchan Joshi <joshi.k@samsung.com>
---
 drivers/nvme/host/nvme.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/nvme/host/nvme.h b/drivers/nvme/host/nvme.h
index 09303454bb24..7bfa410d055e 100644
--- a/drivers/nvme/host/nvme.h
+++ b/drivers/nvme/host/nvme.h
@@ -470,7 +470,7 @@ struct nvme_ns_head {
 	struct nvme_effects_log *effects;
 	u64			nuse;
 	unsigned		ns_id;
-	int			lba_shift;
+	u8			lba_shift;
 	u16			ms;
 	u16			pi_size;
 	u8			pi_type;
-- 
2.25.1



  parent reply	other threads:[~2024-07-30 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240730103941epcas5p37930edd18b9649d4df2083151ed21022@epcas5p3.samsung.com>
2024-07-30 10:31 ` [PATCH 0/3] nvme_ns_head cleanup Kanchan Joshi
2024-07-30 10:31   ` [PATCH 1/3] nvme: remove a field from nvme_ns_head Kanchan Joshi
2024-07-30 15:02     ` Christoph Hellwig
2024-07-31  9:45     ` Sagi Grimberg
2024-07-31 15:36     ` Keith Busch
2024-07-30 10:31   ` Kanchan Joshi [this message]
2024-07-30 15:03     ` [PATCH 2/3] nvme: change data type of lba_shift Christoph Hellwig
2024-07-31  9:46     ` Sagi Grimberg
2024-07-30 10:31   ` [PATCH 3/3] nvme: reorganize nvme_ns_head fields Kanchan Joshi
2024-07-30 15:04     ` Christoph Hellwig
2024-07-31  9:46     ` 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=20240730103138.66714-3-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