From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: unexport nvme_start_keep_alive
Date: Wed, 28 Mar 2018 10:07:06 +0200 [thread overview]
Message-ID: <20180328080706.GC20373@lst.de> (raw)
In-Reply-To: <20180326084015.9269-1-jthumshirn@suse.de>
On Mon, Mar 26, 2018@10:40:15AM +0200, Johannes Thumshirn wrote:
> nvme_start_keep_alive() isn't used outside core.c so unexport it and
> make it static.
>
> Signed-off-by: Johannes Thumshirn <jthumshirn at suse.de>
Looks good:
Reviewed-by: Christoph Hellwig <hch at lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Keith Busch <keith.busch@intel.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme: unexport nvme_start_keep_alive
Date: Wed, 28 Mar 2018 10:07:06 +0200 [thread overview]
Message-ID: <20180328080706.GC20373@lst.de> (raw)
In-Reply-To: <20180326084015.9269-1-jthumshirn@suse.de>
On Mon, Mar 26, 2018 at 10:40:15AM +0200, Johannes Thumshirn wrote:
> nvme_start_keep_alive() isn't used outside core.c so unexport it and
> make it static.
>
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2018-03-28 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 8:40 [PATCH] nvme: unexport nvme_start_keep_alive Johannes Thumshirn
2018-03-26 8:40 ` Johannes Thumshirn
2018-03-28 8:07 ` Christoph Hellwig [this message]
2018-03-28 8:07 ` Christoph Hellwig
2018-03-28 15:07 ` Keith Busch
2018-03-28 15:07 ` Keith Busch
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=20180328080706.GC20373@lst.de \
--to=hch@lst.de \
/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.