From: Christoph Hellwig <hch@lst.de>
To: Anton Eidelman <anton.eidelman@gmail.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, kbusch@kernel.org,
sagi@grimberg.me, axboe@fb.com,
Anton Eidelman <anton@lightbitslabs.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v3 1/2] nvme: fix build error: nvme_mpath_update stub without static
Date: Thu, 24 Mar 2022 07:03:34 +0100 [thread overview]
Message-ID: <20220324060334.GA12261@lst.de> (raw)
In-Reply-To: <20220324003900.1589124-2-anton@lightbitslabs.com>
On Wed, Mar 23, 2022 at 06:38:59PM -0600, Anton Eidelman wrote:
> Fix multiple definition of nvme_mpath_update() on
> builds with CONFIG_NVME_MULTIPATH disabled:
> the stub function is missing "static inline".
Please just resend a new patch. I've dropped the old one from
the nvme-5.18 branch for now.
next prev parent reply other threads:[~2022-03-24 6:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 23:43 [PATCH] nvme: fix build error: nvme_mpath_update stub without static Anton Eidelman
2022-03-24 0:30 ` [PATCH v2 0/2] Fix issues with nvme_mpath_update Anton Eidelman
2022-03-24 0:30 ` [PATCH v2 1/2] nvme: fix build error: nvme_mpath_update stub without static Anton Eidelman
2022-03-24 0:30 ` [PATCH v2 2/2] nvme/mpath: fix crash in nvme_mpath_update for non-ana ctrl Anton Eidelman
2022-03-24 0:38 ` [PATCH v3 0/2] Fix issues with nvme_mpath_update Anton Eidelman
2022-03-24 0:38 ` [PATCH v3 1/2] nvme: fix build error: nvme_mpath_update stub without static Anton Eidelman
2022-03-24 6:03 ` Christoph Hellwig [this message]
2022-03-24 0:39 ` [PATCH v3 2/2] nvme/mpath: fix crash in nvme_mpath_update for non-ana ctrl Anton Eidelman
2022-03-24 6:04 ` Christoph Hellwig
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=20220324060334.GA12261@lst.de \
--to=hch@lst.de \
--cc=anton.eidelman@gmail.com \
--cc=anton@lightbitslabs.com \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@intel.com \
--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.