From: Bjorn Helgaas <helgaas@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: kbuild-all@01.org, linux-pci@vger.kernel.org,
Sergey Miroshnichenko <s.miroshnichenko@yadro.com>
Subject: Re: [pci:review/pci/resource 8/21] drivers/nvme/host/pci.c:2919:6: sparse: symbol 'nvme_rescan_prepare' was not declared. Should it be static?
Date: Tue, 26 Mar 2019 12:35:56 -0500 [thread overview]
Message-ID: <20190326173556.GK24180@google.com> (raw)
In-Reply-To: <20190326154012.GA8171@infradead.org>
[+cc Sergey]
On Tue, Mar 26, 2019 at 08:40:12AM -0700, Christoph Hellwig wrote:
> Please make sure all nvme patches go by the nvme maintainers and have
> an ACK, btw. I've not even seen this patch before.
Thanks for pointing that out! I haven't accepted any of this series
yet; I just pushed the branch to get build checking from the robot in
parallel with reviewing things.
Bjorn
prev parent reply other threads:[~2019-03-26 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 15:37 [pci:review/pci/resource 8/21] drivers/nvme/host/pci.c:2919:6: sparse: symbol 'nvme_rescan_prepare' was not declared. Should it be static? kbuild test robot
2019-03-26 15:37 ` [RFC PATCH pci] nvme-pci: nvme_rescan_prepare() can be static kbuild test robot
2019-03-26 15:40 ` [pci:review/pci/resource 8/21] drivers/nvme/host/pci.c:2919:6: sparse: symbol 'nvme_rescan_prepare' was not declared. Should it be static? Christoph Hellwig
2019-03-26 17:35 ` Bjorn Helgaas [this message]
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=20190326173556.GK24180@google.com \
--to=helgaas@kernel.org \
--cc=hch@infradead.org \
--cc=kbuild-all@01.org \
--cc=linux-pci@vger.kernel.org \
--cc=s.miroshnichenko@yadro.com \
/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.