From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <lkp@intel.com>
Cc: Guixin Liu <kanie@linux.alibaba.com>,
kbuild-all@lists.01.org, linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [linux-nvme:nvme-5.20 6/14] drivers/nvme/host/pci.c:3540:41: error: 'nvme_dev_pm_ops' undeclared here (not in a function); did you mean 'nvme_dev_map'?
Date: Thu, 21 Jul 2022 17:38:38 +0200 [thread overview]
Message-ID: <20220721153838.GB5900@lst.de> (raw)
In-Reply-To: <202207212326.SB1C57On-lkp@intel.com>
I've dropped the patch for now.
prev parent reply other threads:[~2022-07-21 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 15:35 [linux-nvme:nvme-5.20 6/14] drivers/nvme/host/pci.c:3540:41: error: 'nvme_dev_pm_ops' undeclared here (not in a function); did you mean 'nvme_dev_map'? kernel test robot
2022-07-21 15:38 ` Christoph Hellwig [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=20220721153838.GB5900@lst.de \
--to=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox