All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Eidelman <anton.eidelman@gmail.com>
To: Christoph Hellwig <hch@lst.de>,
	linux-nvme@lists.infradead.org, kbusch@kernel.org,
	sagi@grimberg.me, axboe@fb.com
Subject: Re: [PATCH v2 2/3] nvme/multipath: cosmetic: keep ns nsid locally
Date: Mon, 13 Sep 2021 14:19:35 -0600	[thread overview]
Message-ID: <20210913201935.GA83181@anton-latitude> (raw)
In-Reply-To: <20210913160220.GB6442@lst.de>

On Mon, Sep 13, 2021 at 06:02:20PM +0200, Christoph Hellwig wrote:
> On Mon, Sep 13, 2021 at 09:30:22AM -0600, Anton Eidelman wrote:
> > Keep the nsid of the current namespace in a local variable.
> > Change the type to unsigned int to make checkpatch happy.
> > 
> > Signed-off-by: Anton Eidelman <anton@lightbitslabs.com>
> 
> I can't really see any improvement here.  Also checkpath as so often
> these days is fundamentally wrong here.

Do we you prefer to scrap this commit?

I just wanted to get rid of multiple occurances of "ns->head->ns_id",
and just use a local variable that only changes
once in the for_each iteration.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-09-13 20:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-12 18:54 [PATCH RESEND 0/3] nvme/mpath: fix missed namespaces in ana state update Anton Eidelman
2021-09-12 18:54 ` [PATCH 1/3] nvme/multipath: fix failure to update ns ana state Anton Eidelman
2021-09-12 18:54 ` [PATCH 2/3] nvme/multipath: cosmetic: keep ns nsid locally Anton Eidelman
2021-09-12 18:54 ` [PATCH 3/3] nvme/multipath: fix stale ana state for namespaces just added by scan work Anton Eidelman
2021-09-13 15:30   ` [PATCH v2 0/3] nvme/mpath: fix missed namespaces in ana state update Anton Eidelman
2021-09-13 15:30     ` [PATCH v2 1/3] nvme/multipath: fix failure to update ns ana state Anton Eidelman
2021-09-13 16:01       ` Christoph Hellwig
2021-09-13 19:29       ` Sagi Grimberg
2021-09-14  8:27       ` Christoph Hellwig
2021-09-13 15:30     ` [PATCH v2 2/3] nvme/multipath: cosmetic: keep ns nsid locally Anton Eidelman
2021-09-13 16:02       ` Christoph Hellwig
2021-09-13 20:19         ` Anton Eidelman [this message]
2021-09-13 20:57           ` Keith Busch
2021-09-14  5:44             ` Christoph Hellwig
2021-09-13 15:30     ` [PATCH v2 3/3] nvme/multipath: fix stale ana state for namespaces just added by scan work Anton Eidelman
2021-09-13 16:03       ` Christoph Hellwig
2021-09-13 16:08         ` Keith Busch
2021-09-14  6:24           ` Sagi Grimberg
2021-09-14  6:30             ` Christoph Hellwig
2021-09-14  6:40               ` Christoph Hellwig
2021-09-14  7:09               ` Sagi Grimberg
2021-09-14  7:32                 ` Christoph Hellwig
2021-09-14 16:45                   ` Anton Eidelman
2021-09-15  9:32                     ` Sagi Grimberg
2021-09-14 14:24               ` Keith Busch
2021-09-13 16:07       ` Keith Busch
2021-09-13 16:11         ` Christoph Hellwig
2021-09-13 16:24           ` Keith Busch
2021-09-13 16:46           ` Anton Eidelman
2021-09-13 15:32     ` [PATCH v2 0/3] nvme/mpath: fix missed namespaces in ana state update Christoph Hellwig
2021-09-13 15:42     ` [PATCH v2 0/3] nvme/mpath: fix missed namespaces in ana state update FIXED Anton Eidelman
2021-09-13 21:46       ` [PATCH v3 0/3] nvme/mpath: fix missed namespaces in ana state update Anton Eidelman
2021-09-13 21:46         ` [PATCH v3 1/3] nvme/multipath: fix failure to update ns ana state Anton Eidelman
2021-09-13 21:46         ` [PATCH v3 2/3] nvme/multipath: cosmetic: keep ns nsid locally Anton Eidelman
2021-09-13 21:46         ` [PATCH v3 3/3] nvme/multipath: fix stale ana state for namespaces just added by scan work Anton Eidelman

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=20210913201935.GA83181@anton-latitude \
    --to=anton.eidelman@gmail.com \
    --cc=axboe@fb.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 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.